Parts Catalog API Integration

Name: AutoWiz
Author: AutoWiz

Seamlessly bring OEM parts search and VIN lookup into your existing e-commerce platform, ERP, or point-of-sale system — with your own branding.

Request a pilot on your inventory

Built to fit your stack

Rather than asking customers to leave your platform to look up parts, AutoWiz plugs OEM cross-reference and VIN-to-part search directly into the tools you already run, through API endpoints tailored to your data.

The key difference from a generic parts catalog is that results are resolved against your own inventory. A vehicle might have 47 OEM parts mapped to it; your customer only sees the 3 you actually sell, with your SKU, your description and your price. Nobody clicks through to a part you can't ship.

Only the parts you carry

One call takes a plate or VIN and returns the vehicle, how many parts fit it in total, and the subset that exists in your catalog, ready to render as product cards:

Vehicle → your catalog

POST https://api.autowiz.app/api/v2/shop-parts
Authorization: Bearer $AUTOWIZ_API_KEY
{ "car_number_or_vin": "5777638" }

{
  "vehicle": { "vehicle_number": "5777638", "brand": "Mazda", "year": 2016, "name": "CX-5 - Executive" },
  "parts_total": 47,
  "shop_parts_count": 3,
  "parts": [
    {
      "sku": "PE0113440",
      "partdesc": "פילטר אוויר",
      "category_desc": "מסננים",
      "price": 45.5,
      "image": "https://…/PE0113440.jpg"
    }
  ]
}

When a customer arrives with a part number instead of a car, get-compatibles returns every interchangeable and superseded number for it. The matches combine TecDoc-derived data with manually curated cross-references, so an old OE number still finds the current part on your shelf.

OEM number → interchangeable numbers

POST https://api.autowiz.app/api/v2/get-compatibles
{ "oem": "PE0113440" }

["PE0113440A", "PEY113440"]

Where it plugs in

Surface	What the customer or clerk does	API calls
Storefront search	Enters a plate or VIN and browses only fitting products	`shop-parts`
Guided vehicle selector	Picks brand → year → model → engine from drop-downs	`get-0-brands … get-3-parts-by-paramsV4`
Point of sale	Types a part number off an old box and finds the in-stock equivalent	`get-compatibles`
ERP and purchasing	Checks fitment and cross-references before ordering stock	`get-car-parts, get-compatibles`

Because the storefront and the counter call the same API, online search and in-store lookup never disagree about what fits.

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 matches 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: a plate or VIN box that calls shop-parts and renders results with your existing product templates.
4
Validate on real vehicles
Run your own common vehicles and part 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
Language	Vendor's choice	English, with Hebrew brand and model names available

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 vehicle and OEM matches 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.

Which search inputs can our customers use?+

A VIN or Israeli plate number, an OEM part number, or a guided brand, year, model and engine-capacity selection. Brand and model lists are also available with Hebrew names for Hebrew-language storefronts.

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

Plan your integration

Talk to our team about your platform and data, or create an account to get API access directly.

Request a pilot Contact sales