Toyota Parts Breakdown Catalogue API

Enter a VIN / frame number / model year to get the full set of part groups, OEM part numbers, names, quantities and exploded diagrams for that model in seconds.

Built on the public structure of Toyota's global parts catalogue, we clean, standardise and relationship-model vehicle identification, part groups, part details and exploded diagrams, delivered uniformly through a REST API across four major systems: engine, chassis, body and electrical.

No need to maintain a huge parts catalogue and the frequently changing supersession chain yourself.

View integration sample

Enterprise solution enquiryJSON APIPrecise production date split

Identify vehicle: TOYOTA CAMRY (JPP)
Market: North America (US)
Frame number: ACV30L-AEPNKA
Production date: 2002/06
VIN: JTDBE32K******1234

Identified134 groups parsed

Sample part details · CYLINDER HEAD (cylinder head group)

Part number (sample)NameQuantityApplicable

11101-0A010Cylinder head assembly1CAMRY JPP

11298-0A010Cylinder head bolt10CAMRY JPP

90913-02071Spark plug seal4CAMRY JPP

11135-0A010Oil splash valve2CAMRY JPP

134+Part groups (sections) for a single model

4 major systemsEngine / chassis / body / electrical

10–11 charactersToyota OEM part number structure

Accurate to the monthProduction date split (prod_date split)

Why teams need the Toyota Parts Breakdown API

The root cause of "hard to find parts, chaotic pricing, easy to buy wrong" in the auto parts industry is that model-to-part relationships are highly non-standard and change frequently. We turn that into structured data you can get in one call.

Match every part on the vehicle from one VIN

Goodbye to "veteran memory + a stack of catalogues + endless parts-chasing phone calls". Enter a 17-character VIN to resolve the model, model year and trim and get all part groups for that vehicle.

years

Precise production date split

The same model year and trim can differ by production month — brake disc diameter, alternator output, oxygen sensor connector. The API splits by prod_date so you do not buy the wrong part.

Supersedes

Supersession handled automatically

Toyota keeps updating part numbers and old numbers get superseded. The API returns the latest valid part number and the supersession chain, so you never quote a customer with a discontinued number.

Export

Regional part number identification for export

Parts for the Middle East (GCC) and Southeast Asia carry specific suffixes (such as G/E) affecting heat resistance, emissions and compliance. The API annotates regional applicability to support cross-border spares.

The data flow from one query to a usable parts list

Enter at least one identifier and the system resolves the model, matches groups, returns details and exploded diagrams, and applies supersession.

STEP 01

Enter an identifier

Any one of VIN / frame number / model name / model year can start a query.

STEP 02

Resolve vehicle profile

Returns a Vehicle Profile with model, market, frame number, production date, catalogue code and more.

STEP 03

Match part groups

Returns all sections across the four major systems plus the exploded-diagram count per group.

STEP 04

Returns part details

OEM part numbers, names, quantities, applicable models and exploded-diagram callouts for each group.

STEP 05

Apply supersession chain

Applies supersession, returns the latest valid part number and flags superseded ones.

Toyota Parts Breakdown Catalogue · Data API

Below are the standardised endpoints designed by GooFuture (masked demo, no upstream site information). API documentation is not published with this landing page; contact us via WeCom at the bottom of the page for onboarding.

GET

Model identification

/toyota/vehicle/identify

Input:vin or frame or model + prod_date.
Response:Model, market, frame number, production date, catalogue code and total group count.

GET

Part group list

/toyota/sections

Input:Vehicle catalogue code / model_dir.
Response:All sections under the four major systems (name, diagram count, parent system).

GET

Part details

/toyota/parts

Input:Section identifier + model.
Response:Part number, name, quantity, applicable models and exploded-diagram callout numbers.

GET

Part details / supersession chain

/toyota/part/{part_no}

Input:OEM part number.
Response:Name, specification, supersession chain and regional applicability.

GET

Exploded diagram

/toyota/diagram/{section}

Input:Section identifier.
Response:Mapping from exploded diagrams and callout numbers to part numbers.

GET

Direct VIN lookup for a part category

/toyota/vin/{vin}/parts

Input:VIN + category (e.g. brake_pad / oil_filter).
Response:Priority-ordered OEM numbers + quantities + applicability notes.

Integration sample (masked)

Below is a masked response sample for vehicle identification + part details. All VINs are masked and part numbers follow Toyota's public format; this is only to illustrate the field structure and represents no real vehicle.

Sample response · vehicle identification → cylinder head group part details

{
  "request": {
    "vin": "JTDBE32K******1234",
    "frame": "ACV30L-AEPNKA",
    "prod_date": "2002/06"
  },
  "vehicle": {
    "make": "TOYOTA",
    "model": "CAMRY (JPP)",
    "market": "US",
    "sections_total": 134,
    "systems": ["Engine/Fuel/Tool", "Chassis/Driveline", "Body", "Electrical"]
  },
  "section": {
    "code": "cylinder-head",
    "name": "CYLINDER HEAD",
    "diagrams": 1,
    "parts": [
      { "part_no": "11101-0A010", "name": "Cylinder head assembly",   "qty": 1,  "applies_to": "CAMRY JPP" },
      { "part_no": "11298-0A010", "name": "Cylinder head bolt",   "qty": 10, "applies_to": "CAMRY JPP" },
      { "part_no": "90913-02071", "name": "Spark plug seal", "qty": 4, "applies_to": "CAMRY JPP" }
    ]
  },
  "supersession": {
    "11101-0A010": { "status": "active", "supersedes": [] },
    "90913-02071": { "status": "active", "supersedes": ["90913-02020"] }
  }
}

Who uses Toyota parts breakdown data

From parts-market stalls to export e-commerce platforms, the four-level structured relationship of model → system → assembly → part is the foundation of auto parts digitalisation.

Parts dealers / market stalls

Replace "human memory + parts-chasing calls" with an EPC data foundation — enter a VIN to locate every part on the vehicle and solve the core problem of "how do I find the part".

Repair shops / 4S dealerships

Get precise OEM part numbers and exploded diagrams to avoid wrong parts and returns, improving first-time fix rates and customer trust.

Export auto parts e-commerce

Amazon / eBay / independent stores achieve "VIN → OEM number → automatic quote" with supersession handled automatically, noticeably improving conversion.

Used-car dealers / reconditioning

Quickly verify wear parts and OEM spares before reconditioning, generate a transparent spares list and speed up vehicle disposal.

Insurance claims

Identify damaged parts and OEM numbers precisely by model during accident repairs, supporting claims quoting and parts procurement.

Auto parts B2B platforms / model database apps

As an EPC data foundation, it provides VIN resolution and model-to-part relationships to power smart matching engines and end-to-end traceability.

Pricing

Choose by call volume and integration depth; all data is aggregated from the public structure of Toyota's global parts catalogue, and commercial use is governed by the service agreement.

Trial

Validate fields and coverage, low-volume integration

¥0 / trial

Monthly call volume: ≤ 1,000 calls
Models covered: Main Toyota model lines
Endpoints: Identify / group / detail
Technical support: Documentation + tickets

Recommended

Standard

Daily lookups for parts dealers / repair shops

¥1,980 / month

Monthly call volume: ≤ 100,000 calls
Models covered: All Toyota model lines + regions
Endpoints: Includes supersession / exploded diagrams
Technical support: Dedicated onboarding

Enterprise

Export e-commerce / B2B platform integration

¥6,800 / month

Monthly call volume: ≤ 1 million calls
Models covered: All model lines + multiple markets
Endpoints: Full set + direct VIN lookup
Technical support: SLA + customisation

Flagship custom

Large platforms / private deployment

Customised on demand

Monthly call volume: Unlimited
Deployment: Private / hybrid cloud
Data: Custom fields + update frequency
Technical support: Dedicated team

The questions worth confirming before integrating a Toyota parts breakdown API

Straight answers on vehicle identification, part number structure, supersession and commercial integration.

What is the minimum input to look up parts?

Any single identifier works: a full or partial VIN, a frame number, or a model name + model year. The system resolves the model, market, production date and catalogue code, then returns part groups and details.

Are the returned part numbers real? What is the structure?

Toyota OEM part numbers are 10–11 character alphanumeric codes: the first 5 characters are the group number (e.g. 44 = brake), the middle characters are the design revision code and the last 3 are the control number. The API returns part numbers matching this public structure and annotates regional applicability suffixes.

Can it handle "same model year, different production month, different parts"?

Yes. The API splits precisely by production date (prod_date) to separate part differences caused by mid-year engineering changes, so you do not buy the wrong part by querying model year alone.

What is supersession and how does the API handle it?

Supersession means Toyota replaces an old part number with a new one (e.g. 90913-02020 → 90913-02071). The API applies the supersession chain on response, returning the latest valid number and flagging the superseded one, so you never quote a customer with a discontinued number.

Can it be used for automated quoting on export auto parts e-commerce?

Yes. Combined with the direct VIN lookup endpoint, you can get priority-ordered OEM numbers and quantities for a specific category (such as front brake pads or oil filters), enabling an automated "VIN → OEM → quote" workflow.

How often is the data updated?

Toyota models and parts catalogues change continuously with new models, facelifts and supersessions. We sync after each new catalogue release; confirm exact frequency during onboarding.

Can I integrate the data into my own ERP / auto parts system?

Yes. The API can be used in internal systems and integrated into repair management, auto parts e-commerce and B2B trading platforms; commercial usage is governed by the applicable plan and service agreement.

What is the data source?

Built on the public structure and part-number rules of Toyota's global Electronic Parts Catalog (EPC), then collected, cleaned, standardised and relationship-modelled for API delivery. GooFuture is a third-party data service provider.

You no longer maintain a huge parts catalogue yourself.

From vehicle identification, part groups, details and exploded diagrams to the frequently changing supersession chain — we handle it all. Your systems just call the API.

Enterprise consultant onboarding · REST API · JSON responses