Discover/Amayama API
live

Amayama APIamayama.com

Access genuine OEM car parts data from Amayama.com. Search by part number or keyword, get pricing from multiple warehouses, shipping estimates, and vehicle compatibility.

Endpoint health
verified 4d ago
list_brands
list_models
get_part_detail
get_part_info
list_frames
6/6 passing latest checkself-healing
Endpoints
6
Updated
26d ago

What is the Amayama API?

The Amayama API exposes 6 endpoints for querying genuine OEM car parts across brands like Toyota, Nissan, Honda, BMW, and Mercedes-Benz. The search_parts endpoint accepts part numbers or keywords and returns paginated results with pricing summaries, while get_part_detail delivers per-warehouse pricing, shipping estimates, delivery dates, weight, and stock status for any specific part number.

Try it
Page number for pagination
Search query - part number (e.g. '90999-00174') or keywords (e.g. 'brake pad toyota')
api.parse.bot/scraper/292e08e2-9fca-46a2-899c-462f77396869/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
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'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace amayama-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Amayama Genuine Car Parts API — search parts, check pricing, explore catalogue."""
from parse_apis.amayama_genuine_car_parts_api import Amayama, Brand_, PartNotFound

client = Amayama()

# Search for brake pad parts across the catalogue (limit= caps total items fetched)
for part in client.partsummaries.search(query="brake pad toyota", limit=3):
    print(part.name, part.part_number, part.price_from_usd)

# Drill into a single search result to get full warehouse pricing
summary = client.partsummaries.search(query="90999-00174", limit=1).first()
if summary:
    detail = summary.details()
    print(detail.name, detail.mpn, detail.availability, detail.weight)
    for offer in detail.offers:
        print(offer.warehouse, offer.price, offer.shipping_price, offer.delivery_date)

# Get a specific part directly by brand and part number
try:
    part = client.parts.get(brand=Brand_.TOYOTA, part_number="47121-76010")
    print(part.name, part.mpn, part.low_price, part.high_price)
except PartNotFound as exc:
    print(f"Part not found: {exc}")

# Alternative: get_detail returns the same data without the source URL
detail = client.parts.get_detail(brand=Brand_.HONDA, part_number="90999-00174")
print(detail.name, detail.mpn, detail.availability)

# Browse the vehicle catalogue: brands → models → frames
for brand in client.brands.list(limit=3):
    print(brand.name, brand.slug)

# List models for a specific brand using constructible Brand
toyota = client.brand(slug="toyota")
for model in toyota.models.list(limit=3):
    print(model.name, model.slug)

# Get frame/chassis codes for a specific model grouped by market
for market in toyota.list_frames(model="camry", limit=3):
    print(market.market, len(market.frames))

print("exercised: partsummaries.search / summary.details / parts.get / parts.get_detail / brands.list / brand.models.list / brand.list_frames")
All endpoints · 6 totalmissing one? ·

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.

Input
ParamTypeDescription
pageintegerPage number for pagination
queryrequiredstringSearch query - part number (e.g. '90999-00174') or keywords (e.g. 'brake pad toyota')
Response
{
  "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

The search_parts endpoint accepts either an exact part number (e.g. 90999-00174) or a keyword string (e.g. brake pad toyota). When an exact part number is provided and the source resolves it to a single part page, the response sets exact_match: true and returns full part information directly. Keyword searches return paginated results, each result carrying part_number, name, price_from_usd, available, and image_url. Use the page parameter to iterate through total_pages.

Per-Part Data

get_part_detail and get_part_info both accept a brand slug and a part_number (dashes optional). Both return an offers array where each entry includes price, shipping_price, delivery_date, and quantity_available — one entry per warehouse carrying the part. get_part_detail adds mpn, sku, images, weight, low_price, high_price, and an availability string (InStock or OutOfStock). get_part_info returns the same core fields plus a url field and a structured compatibility object that lists models and engine codes the part fits.

Catalogue Navigation

Three endpoints let you traverse the parts catalogue hierarchically. list_brands returns every available manufacturer with name, slug, and url. list_models takes a brand slug and returns all model names and slugs for that brand. list_frames takes a brand and model slug and returns all chassis/frame codes grouped by market (Japan, USA, Europe, Asia and Middle East, etc.), each with a code, title, and url. This hierarchy lets you programmatically enumerate the full parts tree for any supported brand.

Reliability & maintenanceVerified

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.

Last verified
4d ago
Latest check
6/6 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build an OEM part price tracker that monitors low_price and high_price changes across warehouses over time.
  • Populate an auto parts e-commerce catalogue using search_parts keyword results filtered by brand.
  • Verify cross-compatibility for a part number by reading the compatibility.models array from get_part_info.
  • Display multi-warehouse shipping lead times by iterating the offers array from get_part_detail and sorting by delivery_date.
  • Build a chassis-code lookup tool using list_frames to enumerate every frame code for a given model and market region.
  • Automate stock-status checks by polling get_part_detail and alerting when availability changes to InStock.
  • Enumerate all supported brands and models via list_brands and list_models to seed a vehicle-fitment database.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does Amayama have an official developer API?+
Amayama does not publish a public developer API or documented REST interface. The data available through this Parse API is not accessible via any official programmatic endpoint from Amayama.
What does the `offers` array in `get_part_detail` actually contain?+
Each element in offers represents one warehouse that stocks the part. Fields per offer include price (in the listed currency), shipping_price, delivery_date, and quantity_available. The response also surfaces low_price and high_price as top-level fields summarising the range across all offers.
Does `search_parts` behave differently for exact part numbers versus keyword queries?+
Yes. When you pass a known part number and the catalogue resolves it to a single part, the response sets exact_match: true and returns the full part detail inline rather than a list. Keyword queries always return a paginated list with total, total_pages, and a results array of summary objects.
Does the API expose part diagrams or exploded assembly views?+
Not currently. The API returns part images via the images array in get_part_detail, but structured assembly diagrams or illustrated parts catalogs (IPCs) are not included in any endpoint response. You can fork this API on Parse and revise it to add an endpoint targeting assembly diagram pages.
Is historical pricing or price-change history available?+
Not currently. All pricing fields — low_price, high_price, and per-offer price — reflect the current state at the time of the request. No historical price records are returned. You can fork this API on Parse and revise it to build a price-history layer by storing and comparing successive responses.
Page content last updated . Spec covers 6 endpoints from amayama.com.
Related APIs in AutomotiveSee all →
car-part.com API
Search for recycled auto parts across thousands of vehicles and get detailed information on pricing, availability, and specifications from car-part.com. Find the exact parts you need with comprehensive search metadata and individual part details to compare options and locate the best deals.
hondapartsnow.com API
Find and purchase genuine Honda parts and accessories by browsing your vehicle's year, model, and trim, or by searching parts directly and looking up components by VIN number. Manage your shopping experience with real-time cart updates and access to detailed part information across all available Honda categories.
autodoc.es API
Browse vehicle makes, models, and variants on Autodoc.es, then search for specific auto parts by keyword or part number. Retrieve category listings with pricing, full part specifications, OE cross-reference numbers, and vehicle fitment data to compare options and verify compatibility.
autodoc.co.uk API
Find auto parts and check compatibility with your vehicle by browsing makes, models, and engines, then search for parts with detailed specifications and discover equivalent alternatives. Get everything you need to identify the right replacement parts for any car in the Autodoc catalog.
bildelsbasen.se API
Find and browse used car parts from Bildelsbasen's inventory by vehicle make, model, registration number, or OEM part number. Get detailed information about available dismantled parts, including pricing and specifications from listed companies.
napaonline.com API
Search NAPA Auto Parts' catalog to find compatible parts by vehicle type, get detailed product information with reviews, and discover similar products all in one place. Browse by vehicle year, make, and model to quickly locate the right parts and read what other customers think about them.
auto-data.net API
Search and retrieve comprehensive specifications for over 53,500 cars by browsing brands, models, generations, and variants to find detailed performance, engine, dimensions, and drivetrain data. Quickly access the exact automotive information you need without navigating multiple sources.
allcarindex.com API
Browse and search detailed information on over 14,000 automotive brands and 6,000 concept cars, organized by region, country, and model specifications. Discover vehicle data across the world's largest automotive encyclopedia with instant access to brand details, model information, and comprehensive search capabilities.