Amayama APIamayama.com ↗
Access genuine OEM car parts data from Amayama.com. Search by part number, browse by brand/model/frame, and retrieve pricing, availability, and shipping info.
What is the Amayama API?
The Amayama API provides 9 endpoints for querying genuine OEM car parts across brands including Toyota, Nissan, Honda, BMW, and Mercedes-Benz. Use search_parts to find parts by keyword or exact part number, get_part_detail to retrieve per-warehouse pricing and delivery estimates, and list_frames to navigate vehicle chassis codes grouped by market region. Responses include manufacturer part numbers, stock status, shipping prices, and weight.
curl -X GET 'https://api.parse.bot/scraper/292e08e2-9fca-46a2-899c-462f77396869/search_parts?page=1&query=brake+pad+toyota' \ -H 'X-API-Key: $PARSE_API_KEY'
Full-text search over the Amayama parts catalogue by keyword or part number. For exact part number matches, the site redirects to the part detail page and the response includes exact_match=true with full part information. For keyword searches, returns paginated summaries with pricing. 20 results per page.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination |
| queryrequired | string | Search query - part number (e.g. '90999-00174') or keywords (e.g. 'brake pad toyota') |
{
"type": "object",
"fields": {
"page": "integer current page number",
"query": "string the search query echoed back",
"total": "integer total number of matching parts",
"results": "array of part summary objects with part_number, name, url, price_from_usd, available, image_url, brand_slug, part_number_clean",
"exact_match": "boolean present and true when search redirected to a single part detail page",
"total_pages": "integer total number of pages"
},
"sample": {
"data": {
"page": 1,
"query": "brake pad toyota",
"total": 120,
"results": [
{
"url": "https://www.amayama.com/en/part/toyota/4712176010",
"name": "PAD, BRAKE PEDAL",
"available": true,
"image_url": "https://static.amayama.com/schema/toyota-4712176010-1665474089338-big.jpg",
"brand_slug": "toyota",
"part_number": "Toyota 47121-76010",
"price_from_usd": 29.56,
"part_number_clean": "4712176010"
}
],
"total_pages": 6
},
"status": "success"
}
}About the Amayama API
Search and Part Detail
search_parts accepts a free-text query or a manufacturer part number (e.g. 90999-00174). When the query matches a single part exactly, the response includes exact_match: true alongside full part data. Paginated keyword searches return arrays of summary objects with part_number, price_from_usd, available, brand_slug, and image_url. get_part_detail and get_part_info both require a brand slug and part_number; they return an offers array where each entry includes warehouse, price, shipping_price, delivery_date, and quantity_available, plus aggregate low_price and high_price fields. get_part_info additionally returns the url of the part page on Amayama.
Catalogue Navigation
list_brands returns all available manufacturer slugs with no inputs required. Pass a brand slug to list_models to get model slugs, then pass brand and model slugs to list_frames to retrieve chassis codes grouped by market (Japan, USA, Europe, Asia and Middle East, etc.). Each frame object carries a code, slug, and url. list_frame_variations resolves a specific frame to its production periods and trim variants; the page_kind field tells you whether the response is a variation table or a direct catalogue page.
Vehicle-Specific Parts Catalogues
get_frame_catalog takes a raw frame or chassis number (e.g. LWEW162113) and returns the full catalogue index for that vehicle, including groups, schemas with schema_path keys, and a vehicle object containing the manufactured date and grade/options attributes. Pass a schema_path from that response to list_schema_parts to retrieve every part row on a specific diagram, each with a pnc position code, pnc_name, and part_number. These two endpoints together let you enumerate all genuine parts for a precisely identified vehicle without knowing part numbers in advance.
The Amayama API is a managed, monitored endpoint for amayama.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when amayama.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official amayama.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a part number lookup tool that resolves exact MPN queries and returns per-warehouse pricing and availability via
get_part_detail - Aggregate OEM parts price data across multiple warehouses using the
offersarray fieldsprice,shipping_price, anddelivery_date - Generate vehicle-specific parts lists by chaining
list_frames,get_frame_catalog, andlist_schema_partsfor a given chassis code - Populate a catalogue browser by iterating
list_brands,list_models, andlist_framesto index all supported vehicles - Track stock status changes for specific parts using the
availabilityfield (InStock / OutOfStock) returned byget_part_detail - Map chassis codes to production periods and trim configurations using
list_frame_variationsfor fleet or VIN-lookup applications - Identify compatible parts for a specific vehicle frame by resolving
get_frame_catalogschemas and enumerating rows withlist_schema_parts
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Amayama have an official public developer API?+
What does the `offers` array in `get_part_detail` actually contain?+
offers represents a single warehouse listing and includes the warehouse name, price in USD, shipping price, estimated delivery date, and quantity available. The top-level low_price and high_price fields summarise the range across all offers for that part.How does `list_frames` organise chassis codes, and what data does each frame carry?+
list_frames groups frame codes under named market regions (Japan, USA, Europe, Asia and Middle East, etc.). Each frame entry includes code (the label as published on Amayama), slug (used as input to list_frame_variations), title, and url. The total across all markets is returned in total_frames.Does the API return historical pricing data or price trends over time?+
offers array in get_part_detail and get_part_info. Historical or trend data is not exposed. You can fork this API on Parse and revise it to store and compare responses over time to build a price-history layer.Is there a limitation on how `search_parts` handles keyword versus part-number queries?+
exact_match: true and returns full part data directly. For keyword queries, results are paginated summaries — they include price_from_usd and available but not the full offers array. To get per-warehouse offers, follow up with get_part_detail using the brand_slug and part_number_clean from the search result.