A REST API providing access to Toyota Electronic Parts Catalog (EPC) data.
The API is designed to make Toyota parts catalog information accessible programmatically, allowing developers to search vehicles, identify OEM part numbers, find compatible models, browse catalog information, check part substitutions, and work with Toyota EPC data across multiple regions.
Search and identify Toyota vehicles using available vehicle information such as:
- VIN
- Frame number
- Frame prefix
- Model information
- Vehicle catalog information
This can be used as the starting point for locating the correct parts catalog for a specific vehicle.
Identify OEM Toyota part numbers through the EPC catalog structure.
Typical workflow:
- Identify the vehicle
- Select the appropriate catalog
- Browse the illustrated parts index
- Identify the required component
- Retrieve the corresponding Toyota part number
Search using a Toyota part number to determine which:
- Vehicles
- Models
- Model codes
- Catalogs
use that particular part.
This is useful for part compatibility and cross-model research.
Search Toyota EPC data using a known OEM part number.
The API can be used to retrieve available information associated with the part and its catalog applications.
Search parts using:
- Part name
- Part description
- Part Name Code (PNC)
This allows parts to be discovered even when the exact OEM part number is unknown.
Retrieve recently introduced parts from a Toyota catalog.
This functionality can be useful for identifying newly added or updated OEM parts.
Access Toyota part-number substitution information.
This can help identify:
- Superseded part numbers
- Replacement part numbers
- Previous part numbers
- Part-number relationships
Useful when an older Toyota OEM number has been replaced by a newer number.
Search parts according to vehicle applicability codes and characteristics such as:
- Engine
- Grade
- Drive configuration
- Drive position
- Other EPC applicability attributes
This helps narrow parts to specific vehicle configurations.
Retrieve available Toyota EPC list-price information.
Note: Pricing availability may depend on the EPC region and dataset. For example, some list-price data may be available only for the Japan dataset.
Retrieve vehicle-related information available within the EPC catalog.
Depending on the available dataset, this can include information used to determine the correct catalog and vehicle configuration before searching for parts.
Browse Toyota EPC catalogs associated with vehicles, models, regions, and catalog configurations.
The EPC data supports multiple geographic data areas.
The underlying EPC system contains multiple regional datasets, including:
| Area | Region |
|---|---|
| EU | Europe |
| GR | General |
| US | United States |
| JP | Japan |
The number of available catalogs may vary depending on the dataset and version being used.
Toyota EPC information can be organized according to:
- Data area / region
- Data language
- Catalog configuration
This allows applications to select the relevant EPC dataset before performing searches.
Access available Toyota J-PIO accessory catalog information.
This can be used for researching Toyota accessories and related catalog data where available.
The Toyota EPC API can be used for applications such as:
- Auto parts websites
- Toyota parts lookup systems
- OEM parts catalogs
- Automotive marketplaces
- Parts compatibility tools
- Vehicle repair applications
- Workshop software
- Inventory management systems
- Parts research platforms
- VIN and frame-based parts lookup
- Toyota part-number cross-reference systems
A typical parts lookup workflow may look like:
VIN / Frame Number
↓
Vehicle Identification
↓
Toyota EPC Catalog
↓
Part Group / Illustration
↓
Part Name Code (PNC)
↓
OEM Part Number
↓
Part Application / Compatibility
↓
Substitution History
Another workflow can start directly from a known part number:
Toyota Part Number
↓
Part Search
↓
Applicable Models
↓
Catalogs
↓
Vehicle Configurations
↓
Replacement / Superseded Numbers
The underlying EPC system supports quick searches using information such as:
Use a VIN or Toyota frame prefix to locate relevant vehicle and catalog information.
Use an OEM Toyota part number to search its EPC applications and associated information.
The exact available endpoints depend on the current API version.
Examples of functionality exposed through the API may include:
Vehicle Search
Catalog Search
Part Number Search
Part-to-Model Search
Part Name / PNC Search
New Parts
Part Substitutions
Applicability Search
Vehicle Information
List Price
Data Areas
See the API documentation for the complete endpoint list, request parameters, and response formats.
API responses are returned in JSON format.
Example:
{
"success": true,
"data": []
}The actual response structure depends on the endpoint being used.
Authentication requirements depend on how the API is deployed.
If an API key is required, include your API key with each request according to the API documentation.
Example:
Authorization: Bearer YOUR_API_KEYor:
X-API-Key: YOUR_API_KEYUse the authentication method specified by the API deployment.
Toyota EPC information can vary by:
- Market
- Region
- Production date
- Model
- Frame number
- Engine
- Grade
- Vehicle configuration
A part appearing on one Toyota model does not necessarily mean that it is compatible with every vehicle using the same model name.
For accurate results, vehicle-specific information should be used whenever possible.
This project is an independent API and is not affiliated with, endorsed by, or sponsored by Toyota Motor Corporation.
Toyota, Toyota model names, trademarks, logos, part numbers, and related identifiers are the property of their respective owners.
The API provides access to catalog information for informational and application-development purposes. Users should independently verify part compatibility before ordering, selling, or installing automotive components.
If you encounter an issue with the API, please provide:
- Endpoint used
- Request parameters
- Example request
- Response received
- Expected response
- Vehicle or part number involved, when applicable
For feature requests, please describe the additional Toyota EPC functionality or endpoint you would like to see added.
Please refer to the repository license for usage terms and restrictions.
From your screenshot specifically, I can identify these EPC functions:
1. **Part Number Translation** – identify the vehicle, browse the illustrated index, and obtain part numbers.
2. **Part Number Application to Models** – find which models/catalogs contain a given part number.
3. **New Parts List** – recently introduced parts for a catalog.
4. **Part Number List** – search by part name or Part Name Code (PNC).
5. **List Price** – list price for a part number; screenshot indicates JP data only.
6. **Applicability Search** – search based on engine, grade, drive position, etc.
7. **Data Configuration** – information about what EPC tables/data are loaded.
8. **Area / Language Setup** – choose EPC area and data language.
9. **J-PIO Accessories** – visible at the bottom of the menu.
10. **VIN/frame prefix lookup**.
11. **Part-number quick lookup**.
12. **Catalogs**.
13. **Part → Models**.
14. **Substitution History**.
15. **Abbreviations**.
16. **Vehicle Information**.
The screenshot also shows four data areas: **Europe (EU), General (GR/GE), United States (US), and Japan (JP)**.
If you send me the **actual endpoint names/URLs for your Toyota EPC API**, I can turn this into a much stronger GitHub README with a proper **Endpoints table, parameters, curl examples, Python examples, JavaScript examples, and real JSON responses** instead of placeholders.