Parts Catalog API Integration
Bring OEM cross-reference search into your existing e-commerce platform, ERP, or point-of-sale system — with your own branding, resolved against your own stock.
Request a pilot on your inventoryBuilt to fit your stack
Rather than asking customers or counter staff to leave your platform to look up equivalents, AutoWiz plugs OEM cross-reference directly into the tools you already run, through API endpoints tailored to your data.
The key difference from a generic cross-reference catalog is that results are resolved against your own inventory. An OEM number may have dozens of equivalents worldwide; your customer only sees the ones you actually sell. Nobody clicks through to a part you can't ship.
Only the parts you carry
One call takes an OEM number and returns every interchangeable and superseded number for it that exists in your catalog. The matches combine TecDoc-derived data with manually curated cross-references, so an old OE number still finds the current part on your shelf.
POST https://api.autowiz.app/api/v2/get-compatibles
Authorization: Bearer $AUTOWIZ_API_KEY
{ "oem": "PE0113440" }
["PE0113440A", "PEY113440"]Where it plugs in
| Surface | What the customer or clerk does | API calls |
|---|---|---|
| Storefront search | Types an OEM number and sees the equivalents you sell | get-compatibles |
| Point of sale | Types a part number off an old box and finds the in-stock equivalent | get-compatibles |
| ERP and purchasing | Checks cross-references and supersessions before ordering stock | get-compatibles |
Because the storefront and the counter call the same API, online search and in-store lookup never disagree about what replaces what.
The typical 7-day path
- 1
Scope and API key
A technical call to pick the first surface and map your SKU format. You generate an API key from your AutoWiz account and make your first authenticated call.
- 2
Sync your catalog
Your stock list is synced to AutoWiz, typically from a daily inventory export, so cross-references are filtered to what you carry. AutoWiz receives a copy and never writes back to your systems.
- 3
Build the first surface
Usually storefront search: an OEM number box that calls get-compatibles and renders results with your existing product templates.
- 4
Validate on real part numbers
Run your own common OEM numbers through it before launch, not a curated demo, then go live and extend to POS and ERP.
Embedded widget vs. API integration
| Third-party widget | AutoWiz API | |
|---|---|---|
| Look and feel | Vendor's UI inside your page | Your templates, your branding |
| Results | Vendor's catalog | Filtered to your inventory |
| Channels | Usually web only | Web, POS, ERP from one API |
What's included
Custom API endpoints
Endpoints mapped to your own data model, not a rigid one-size-fits-all schema.
Your branding
White-label the search experience so customers stay on your platform, under your brand.
Dedicated support
A direct line to our team while you scope, build, and ship the integration.
Analytics included
Track search volume, match rates, and inventory utilization once you're live.
Frequently asked questions
What systems can AutoWiz integrate with?+
AutoWiz integrates with e-commerce platforms, ERP systems, point-of-sale software, and custom applications through a documented REST API. Anything that can send an HTTPS POST with JSON can call it.
Do we have to move our catalog into AutoWiz?+
No. Your product catalog stays the system of record. AutoWiz receives a regular copy of your stock list, typically a daily inventory export, so OEM cross-references can be filtered to what you actually stock. Your storefront keeps rendering products from its own data.
Can we white-label the search experience?+
Yes. The API returns plain JSON with no AutoWiz branding, so results render in your own templates. Custom API endpoints are available when your data model needs a different response shape.
What do our customers search with?+
An OEM part number: the number printed on the old part or its box, quoted by a workshop, or taken from the manufacturer's catalog. AutoWiz returns the interchangeable, superseded and equivalent numbers you carry. The API doesn't decode VINs or return a vehicle's parts list.
Do we get dedicated support during integration?+
Custom integration customers get dedicated support to scope endpoints, map data fields, and get to production quickly.
How long does a custom integration take?+
Most integrations are completed within 7 days from the first technical call, depending on the complexity of your existing systems. Starting with a single surface, usually storefront search, is the fastest path.
Related guides
- Spare Parts API: How to Integrate Auto Parts Data Into Your PlatformWhat a spare parts API is, the common integration surfaces (storefront, POS, ERP), and how to plan a rollout without a quarter-long project.
- How to Add Auto Parts Search to Shopify and WooCommerceWhy generic storefront search fails for auto parts, the two common ways to add fitment-accurate parts search to Shopify or WooCommerce, and what a real integration looks like.
Plan your integration
Talk to our team about your platform and data, or create an account to get API access directly.
