OEM Parts Cross-Reference API
Send any OEM part number and get back every compatible and superseded part from your own inventory, in milliseconds. Built for independent aftermarket retailers, distributors and e-commerce platforms that need accurate cross-reference matching at API speed.
Request a pilot on your inventoryWhat an OEM parts API does
Every part sold in the aftermarket traces back to an OE number: the number the vehicle manufacturer gave the part. The same part is sold under other numbers too, by aftermarket brands, by suppliers who resell it under their own label, and by the manufacturer itself after it revises the number. An OEM parts API turns that tangle into one lookup: send the number you have, get the numbers you can sell.
AutoWiz covers both directions of the match. OE-to-aftermarket answers which replacement parts fit in place of an OE number. OE-to-OE resolves supersessions, so an old number read off a box or an invoice still finds today's part. For the difference between cross-reference, interchange and fitment, see our cross-reference software buyer's guide.
How it works
- 1
Send an OE part number
Your storefront, counter screen or ERP posts the number to the API. Spaces and dashes are ignored, so numbers can be sent as customers type them.
- 2
We resolve it to the original part
The number is matched to the manufacturer's original part, including its superseded and interchangeable OE numbers.
- 3
Get back the parts you stock
Matches are resolved against your own catalog, so the response lists your part numbers: no dead-end results pointing to inventory you don't have.
One request, one answer
curl -X POST https://autowiz.app/api/v3/parts/compatibles \
-H "Authorization: Bearer $AUTOWIZ_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "partNumber": "<OE part number>" }'[
"BRK-1042",
"BRK-1188"
]Requests authenticate with an API key from your account. The full reference, with every endpoint, error and rate limit, is in the documentation you get with the key.
Built for the independent aftermarket
| Who | What they use it for |
|---|---|
| Online parts stores | A search box that finds the right part from the OE number the customer types, current or superseded. |
| Counter and POS staff | Turning the number on an old part or a workshop's quote into the part on your shelf, without leafing through catalogs. |
| Distributors and purchasing | Seeing which OE numbers one SKU already covers before buying another, so equivalent stock isn't bought twice. |
| Brands and suppliers | Mapping the OE numbers your parts replace, so customers searching by OE number find your products. |
Why retailers use it
Instant cross-reference
Millisecond-speed matching means the API can power live search boxes, not just batch jobs.
Matches your own stock
Results are always resolved against your inventory, so customers only see parts you can actually sell.
Combined data sources
TecDoc-derived matches are combined with manually curated cross-references, so superseded and interchangeable numbers resolve to the same part.
Live in 7 days
A RESTful API with full documentation: most teams are fully integrated in about a week, not a quarter.
Frequently asked questions
What is an OEM parts API?+
An OEM parts API lets your software ask about original equipment (OE) part numbers over HTTP instead of looking them up by hand. AutoWiz's answers one question: given an OE number, which parts are equivalent to it, and which of those do you stock.
What does the OEM Parts API return?+
Given an OEM part number, the API returns a JSON list of the part numbers in your own inventory that are a verified compatible match. An account without a catalog of its own gets the compatible OE numbers instead.
Does it handle superseded part numbers?+
Yes. Superseded and interchangeable OE numbers resolve to the same part, so a lookup on an old number printed on a box or an invoice finds the part you stock under its current number.
How fast is a lookup?+
Cross-reference matching runs in milliseconds per request, so it can sit directly behind a live storefront or point-of-sale search box.
How long does integration take?+
AutoWiz is a RESTful API with full documentation. Most retailers, ERPs, and e-commerce platforms are fully integrated within 7 days.
Does it work with my existing inventory?+
Yes. Matches are resolved against your own stock, so results only ever surface parts you actually have available.
Can I look up parts by VIN?+
No. The API starts from an OEM part number and returns its cross-references. It doesn't decode VINs or return the original part numbers for a vehicle, so you need the OEM number first, from the old part, the manufacturer's catalog, or the workshop.
Related guides
- Auto Parts Cross-Reference Software: 2026 Buyer's GuideHow auto parts cross-reference and interchange software works, how it differs from fitment, the 4 tool types, and how to test vendors on your own parts.
- Automotive Parts Compatibility Databases: How Leading Providers Structure Their DataWhat a parts compatibility database actually stores, how leading providers structure fitment and supersession data, and the structural mistakes that break cross-reference accuracy.
- OEM Parts Authoring: What It Means and Why Data Structure MattersWhat OEM parts authoring is, why the quality of authored data determines downstream search accuracy, and what a well-structured authoring process looks like.
Get API access
Create an account to generate an API key, or reach out and we'll help you scope the integration.
