7zap API

From a VIN to the engine code, the gearbox and the maker's own parts catalogue

The 7zap API decodes a 17-character VIN against 7zap's OEM parts catalogue, which covers 70 car makes, and returns the make, model, generation and year plus, where the maker's catalogue has them, the engine code, gearbox, body, market and production date as JSON.

endpoints
2
credits per call
2

2 credits per call≈ $2/1,000 calls1,000 free credits, no card

POST/7zap/v1/vin_decode200
label

Hyundai · Tucson NX4 · G32X (1600 cc · petrol) · M33W (DCT - 7…

vin
TMAJC81BGPJ324179
make
Hyundai
series
Tucson
model
Tucson NX4
generation
Tucson NX4
Real result, captured Nov 19, 2026
Try it live

Run the call yourself, on the real endpoint

Change a parameter and press Try it. The response on the right is what your code will receive.

7zap API

2 of 2 endpoints, ready to run

View docs ↗

Decode one VIN: make, model, generation, year, and where the maker's catalogue has them the engine code, gearbox, body, market and production date, plus the Autodoc maker for the next call.

2 credits1 required · 2 optional
POST/7zap/v1/vin_decode
ok1901 ms · 1 records · sample
{
  "ok": true,
  "meta": {
    "api": "7zap",
    "endpoint": "vin_decode",
    "mode": "live",
    "latency_ms": 1900.8,
    "record_count": 1,
    "cache_hit": false
  },
  "data": {
    "vin": "TMAJC81BGPJ324179",
    "wmi": {
      "wmi": "TMA",
      "region": "Europe"
    },
    "make": "Hyundai",
    "make_slug": "hyundai",
    "series": "Tucson",
    "model": "Tucson NX4",
    "generation": "Tucson NX4",
    "year": 2023,
    "attributes": {
      "Year": "2023"
    },
    "image_url": "https://img.7zap.com/images/oem/models/Hyundai_Tucson_NX4.webp",
    "vehicle_code": "veh_2Qsb5wpyp8m-9j1AcJLO3wFCjgRHqSXt_KW8W9Lvf9w",
    "variants": [
      {
        "index": 0,
        "label": null,
        "badges": [],
        "vehicle_code": "veh_2Qsb5wpyp8m-9j1AcJLO3wFCjgRHqSXt_KW8W9Lvf9w"
      }
    ],
    "decode_source": "decode_vehicle",
    "year_is_estimate": false,
    "details_status": "ok",
    "generation_years": {
      "from": 2020,
      "to": 2024
    },
    "catalog_region": {
      "code": "europe",
      "name": "Europe"
    },
    "vehicle_type": "car",
    "label": "Hyundai · Tucson NX4 · G32X (1600 cc · petrol) · M33W (DCT - 7 SPEED 2WD) · WAGON - 5DR 5P · EUR · 2023",
    "engine": "G32X (1600 cc · petrol)",
    "transmission": "M33W (DCT - 7 SPEED 2WD)",
    "body": "WAGON - 5DR 5P",
    "drive": null,
    "steering": null,
    "market": "EUR",
    "trim": null,
    "production_date": "2023-02-27",
    "production_window": null,
    "specification": [
      {
        "name": "engine",
        "value": "G32X (1600 cc · petrol)"
      },
      {
        "name": "transmission",
        "value": "M33W (DCT - 7 SPEED 2WD)"
      },
      {
        "name": "body",
        "value": "WAGON - 5DR 5P"
      }
    ],
    "generation_image_url": "https://img.7zap.com/images/oem/models/Hyundai_Tucson_NX4.webp",
    "catalog_url": "https://7zap.com/en/catalog/cars/hyundai/tucson-nx4-parts-catalog/#region=europe&vehicle_code=veh_2Qsb5wpyp8m-9j1AcJLO3wFCjgRHqSXt_KW8W9Lvf9w",
    "generation_url": "https://7zap.com/en/catalog/cars/hyundai/tucson-nx4-parts-catalog/",
    "autodoc": {
      "maker": "hyundai",
      "series_hint": "Tucson",
      "vehicle_lookup": {
        "maker": "hyundai"
      },
      "vehicle_by_vin": {
        "vin": "TMAJC81BGPJ324179"
      },
      "vin_search_measured_for_make": true,
      "note": "autodoc vehicle_lookup {maker} lists the model families; pick the one matching series_hint, then generation and engine variant. autodoc vehicle_by_vin tries Autodoc's own VIN search (measured for Mercedes, Skoda, Peugeot, Volvo, Hyundai, Opel, Dacia)."
    }
  }
}
Real response, fetched from the live endpoint with the parameters on the left — trimmed to the first few rows, with seller names left out. Press Try it for the untrimmed response.

Try every endpoint in the playground

Endpoints

What 7zap endpoints does ReefAPI ship?

2 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.

2 endpoints

vin_decode

2 cr

Decode a 17-character VIN with 7zap's OEM catalogue.

required
vin
optional
language, details

parts_catalog

2 cr

The OEM parts-catalogue structure of one car, as 7zap shows it.

required
—
optional
vin, vehicle_code, make, query, group, language, thumbnails

Every parameter, every allowed value →

Missing a 7zap endpoint, or need a source we don't have yet?Contact us real people · same-day reply.
How it works

How the 7zap API works

7zap is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.

01
Authenticate
x-api-key header

No OAuth app, no request signing, no per-site account. One key covers all 694 engines.

02
Call
POST /7zap/v1/…

Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.

03
Pay
2 credits per call

Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.

04
Read
{ ok, data, meta, error }

One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.

Recipe

From a VIN to brake pads with prices for that exact car

7zap says what the car is; Autodoc says what fits it and what it costs. Run end to end on 2026-11-19 with the VIN of a 2015 Opel Insignia 2.0 CDTI (103 kW) from a Czech listing.

01vin_decode
POST/7zap/v1/vin_decode
{"vin": "W0LGT8GS1F1095696"}

Opel Insignia A, 2015, engine LHV (2000 cc diesel), gearbox MYJ 6-speed manual, built 2015-07-14. autodoc.maker is opel.

02parts_catalog
POST/7zap/v1/parts_catalog
{"vin": "W0LGT8GS1F1095696", "query": "brake"}

21 of the car's 744 catalogue assemblies, each with the maker's applicability codes, for example A20DTE[LHV] diesel engines.

03vehicle_lookup
POST/autodoc/v1/vehicle_lookup
{"maker": "opel", "model": "insignia", "generation": "insignia-2008"}

Autodoc's 29 Insignia A engine variants. 7zap gives the engine code and size, not the power, so the listing's 103 kW picks the 2.0 CDTI variant 20739-2-0-cdti-68.

04search
POST/autodoc/v1/search
{"category": "brake-pad-set-10130", "maker": "opel", "model": "insignia", "generation": "insignia-2008", "vehicle": "20739-2-0-cdti-68", "market": "de"}

20 brake pad sets for that engine variant on autodoc.de, 13.99 to 56.99 EUR, each with brand, rating and the manufacturer's part number.

The exact car from its VIN, the maker's catalogue assemblies for it, and priced parts that fit it.

request
curl -X POST https://api.reefapi.com/7zap/v1/vin_decode \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"vin":"WVWZZZAUZLW053403"}'
response envelope
{
  "ok": true,
  "data": { … },
  "meta": {
    "api": "7zap",
    "endpoint": "vin_decode",
    "mode": "live",
    "latency_ms": …,
    "record_count": …
  },
  "error": null
}
Fields

What a VIN decode returns, make by make

Three live answers from 2026-11-19. How much of the factory specification comes back depends on what the maker's own catalogue publishes, so the same call returns an engine code for the Hyundai and the Opel and a body code and production window for the Volkswagen.

FieldHyundai Tucson, TMAJC81BGPJ324179Opel Insignia, W0LGT8GS1F1095696VW Golf, WVWZZZAUZLW053403
make, modelHyundai, Tucson NX4Opel, Insignia AVolkswagen, Golf A7 Facelift
year202320152020
engineG32X (1600 cc, petrol)LHV (2000 cc, diesel)null: VW-group catalogues give no engine here
transmissionM33W (DCT, 7 speed, 2WD)MYJ (manual, 6 speed)null
bodyWAGON - 5DR 5PnullAU (body code)
marketEURnullnull
production_date / production_window2023-02-272015-07-14window 2019-07-01 to 2020-08-31
generation_years2020 to 20242009 to 20172017 to 2027
specification[]14 facts, including engine number and transmission number4 facts4 facts
autodoc.makerhyundaiopelvw

A field the maker's catalogue does not publish comes back as null; nothing is filled in by guesswork. year is 7zap's year, which can be the model year or the build year. When 7zap only knows the generation's first year the answer says year_is_estimate: true: a Mercedes C-Class listed as 2020 came back as 2015 and a Citroen C4 Picasso listed as 2008 as 2004, both flagged.

Coverage

Measured on 34 real European VINs

Live calls on 2026-11-19. The VINs came from Czech used-car listings, so every answer was checked against what the seller wrote. Some of these lines go against us.

VINs decoded

21 of 34, with the make and model right on all 21. The other 13 came back as NOT_FOUND. None of the 34 calls failed or returned an empty success.

Makes that decoded

Volkswagen, Audi, Seat, Cupra, Skoda, BMW, Mercedes-Benz, Opel, Renault, Dacia, Citroen, Fiat, Hyundai, Kia, Toyota and Nissan. 7zap's catalogue lists 70 makes in all.

Engine code

Returned for 12 of the 21 and equal to the seller's engine every time: BMW 116i N43, BMW X7 40d B57, three 1.6 T-GDI (Hyundai Tucson, two Kia Sportage), Hyundai i30 1.0 T-GDi, Toyota Corolla 1.4 4ZZ-FE, Opel Insignia 2.0 CDTI LHV, Citroen C4 Picasso 1.6 HDi DV6TED4, Nissan Qashqai 1.2 DIG-T HRA2DDT, Renault Clio 1.0 TCe H4D, Dacia Duster 1.6 K4M. Volkswagen, Audi, Seat, Cupra and Skoda return the body code, year and production window instead.

Year

Equal to the listing on 14 of 21. 4 were one year apart because 7zap gives the model year or the build date; 2 were the generation's first year and are flagged year_is_estimate: true (Mercedes C-Class, Citroen C4 Picasso); 1 listing had no year.

Not found in this test

Ford (0 of 2), Peugeot (0 of 2), Volvo (0 of 2), Mazda (0 of 1), Tesla (0 of 1), and one of two VINs each for Mercedes, Opel, Renault, Skoda and Dacia. Autodoc's own VIN search (vehicle_by_vin in the Autodoc API) found the Peugeot, the Volvo and the Mercedes GLC; on the 13 VINs tried on both, the two together found 12.

Parts catalogue

15 of 15 calls answered. 229 assemblies on a Toyota Corolla, 744 on an Opel Insignia, 1,048 on a VW Polo, 1,510 on a VW Golf. brake on the Polo kept 30, water pump on a BMW 116i 2 of 986, clutch on a Kia Sportage 15 of 270.

Maker's wording

Filters match the maker's own names: Toyota says Headlamp (headlight finds 0, headlamp 2) and Mercedes says spring strut, not shock absorber. A zero is returned as an empty result with the car still described.

Languages

32, the ones 7zap offers. Russian translated a Volkswagen catalogue's group names; Latvian left BMW's names in English, as 7zap has them.

Not included

OE part numbers (7zap shows them only to signed-in members), part prices and full-size diagrams. Prices come from the Autodoc API, one call after the decode.

Use cases

What people build with 7zap

The jobs this data is most often used for.

2

endpoints

2

credits per call

01

Parts shops: the customer types a VIN and sees the exact generation, engine code and gearbox before choosing a part.

02

VIN to parts with prices: decode with 7zap, then list the Autodoc parts that fit that engine variant.

03

Used-car listing checks: compare the seller's model, year and engine with what the maker's catalogue says for the VIN.

04

Garage and fleet software: store engine code, gearbox and production date per vehicle from the VIN alone.

Pricing

What 7zap data costs

The cheapest call here is 2 credits, so $15/mo (Pro) buys 5,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.

Full pricing →
$0.67–$1.50 / 1,000 credits
  • 1,000 free credits on signup, no card
  • One key, all 694 APIs, one credit pool
  • Failed and blocked calls are never charged
  • Credits roll over and never expire
no credit card1,000 free credits · instant API key · pay by card or crypto
Quickstart

Call it in two lines

Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.

curl
curl -X POST https://api.reefapi.com/7zap/v1/vin_decode \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"vin":"WVWZZZAUZLW053403"}'
python
import os
import requests

REEF_KEY = os.environ["REEF_KEY"]

r = requests.post(
    "https://api.reefapi.com/7zap/v1/vin_decode",
    headers={"x-api-key": REEF_KEY},
    json={
        "vin": "WVWZZZAUZLW053403"
    },
    timeout=90,
)
print(r.json()["data"])
FAQ

Have a question? We got answers.

The questions people actually ask before wiring up 7zap.

Is there a VIN decoder API that returns the engine code?▾

Yes. 7zap's vin_decode returns the engine code from the maker's own parts catalogue when the catalogue has it: N43 for a 2009 BMW 116i, B57 for a 2023 BMW X7 40d, G32X (1600 cc petrol) for a 2023 Hyundai Tucson, LHV (2000 cc diesel) for a 2015 Opel Insignia 2.0 CDTI, H4D for a 2020 Renault Clio 1.0 TCe, K4M for a 2012 Dacia Duster 1.6. On 34 real European VINs tested on 2026-11-19 an engine came back for 12 cars and matched the seller's listing on all 12.

Which car makes does the 7zap VIN decoder work for?▾

7zap's catalogue has 70 makes. In the 2026-11-19 test, VINs decoded for Volkswagen, Audi, Seat, Cupra, Skoda, BMW, Mercedes-Benz, Opel, Renault, Dacia, Citroen, Fiat, Hyundai, Kia, Toyota and Nissan, with the make and model right on all 21 decoded cars. The engine code comes with BMW, Hyundai, Kia, Toyota, Opel, Nissan, Renault, Dacia and Citroen; Volkswagen-group cars (VW, Audi, Seat, Cupra, Skoda) return the body code, year and production window instead.

What happens with a VIN 7zap does not know?▾

You get a NOT_FOUND error instead of a made-up car. 13 of the 34 test VINs ended that way: both Fords (Transit Custom, Tourneo Custom), both Peugeots (308, 408), both Volvo XC60s, a Mazda CX-60, a Tesla Model 3, and one of two VINs each for Mercedes, Opel, Renault, Skoda and Dacia. For Peugeot, Volvo and the Mercedes GLC, Autodoc's own VIN search did find the car: use vehicle_by_vin in the Autodoc API. Run on the same 13 VINs, 7zap found 8 and Autodoc 7, and together they found 12.

How accurate is the year?▾

On the 21 decoded test cars the year equalled the listing 14 times. 4 were one year apart because 7zap gives the model year or the build date (a Golf listed as 2019 came back as 2020, built in the window 2019-07 to 2020-08). 2 were the first year of the generation and came with year_is_estimate: true, and 1 listing gave no year to compare.

Does it return OEM part numbers?▾

No. parts_catalog returns the structure of the car's catalogue (groups, subgroups and assemblies with the maker's applicability codes and a diagram thumbnail) but no part numbers, because 7zap shows those only to signed-in members. For parts with numbers and prices that fit the decoded car, go on to the Autodoc API.

How do I get parts with prices for a decoded VIN?▾

Every decode carries an autodoc block with Autodoc's maker slug. Measured on 2026-11-19: a 2015 Opel Insignia VIN decoded to engine LHV (2.0 diesel); Autodoc's vehicle_lookup for opel, insignia, insignia-2008 listed the 2.0 CDTI 103 kW variant as 20739-2-0-cdti-68, and Autodoc's search for brake pads on that variant returned 20 sets on autodoc.de from 13.99 to 56.99 EUR, all marked as fitting that car.

What does parts_catalog return, and how do I filter it?▾

The car's catalogue tree: top-level groups such as Engine, Transmission, Chassis, Body, Interior, Electrical and Maintenance, their subgroups and the assemblies under them, each with its name, the maker's applicability codes (for example A20DTE[LHV] diesel engines on the Insignia) and a diagram thumbnail. query keeps assemblies whose name contains your words: brake on a VW Polo kept 30 of 1,048, water pump on a BMW 116i 2 of 986. The words follow the maker: Toyota says Headlamp, so headlight finds nothing there, and Mercedes says spring strut rather than shock absorber.

Which languages are supported?▾

The 32 languages 7zap's own site offers, from English, German, French, Spanish and Polish to Latvian, Russian, Ukrainian, Turkish, Arabic, Japanese and Chinese. Names are translated where 7zap translates them: Russian gave Russian group names on a Volkswagen catalogue, while Latvian left BMW's names in English.

Is this an official 7zap API?▾

No. It is an independent API that returns what 7zap's public catalogue shows as JSON. You need no 7zap account, only a ReefAPI key.

What is the 7zap API?▾

7zap API is a ReefAPI endpoint group for vin decoder with the engine code, gearbox and production date from the maker's catalogue, plus the car's oem parts-catalogue groups, for 70 car makes. It returns live JSON through POST requests under /7zap/v1.

Is the 7zap API free to try?▾

Yes. ReefAPI starts with 1,000 free credits, no card required. 7zap calls use the same shared credit balance as every other ReefAPI engine.

Do I need a 7zap login or account?▾

No login to 7zap is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

How fresh is the 7zap data?▾

The page example is captured from a live vin_decode call, and production requests fetch live data through ReefAPI rather than a static sample.

How many credits does the 7zap API use?▾

7zap actions currently cost 2 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Contact

Need something this API does not do?

Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.

0/4000

No account needed · we reply from [email protected]

Try it on your own data before you pay anything

The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 693 APIs, and the same envelope everywhere.

Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-19.