7zap API & Scraper
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.
🤖 Using an AI assistant? Copy this link into ChatGPT / Claude / Cursor — it reads every endpoint and parameter instantly and tells you if this API fits your use case.
vin_decode also returns the generation's production years and catalogue region, every factory fact 7zap lists for the car in its own words (on a 2023 Hyundai Tucson: 14 facts, including the engine and gearbox serial numbers), a picture of the generation and 7zap's catalogue link for that exact car. Tested on 2026-11-19 with 34 real European VINs taken from Czech used-car listings: 21 decoded, and the make and model were right on all 21. An engine code came back for 12 of them (BMW, Hyundai, Kia, Toyota, Opel, Nissan, Renault, Dacia, Citroen) and it matched the engine the seller listed every time; Volkswagen, Audi, Seat, Cupra and Skoda return the body code, year and production window instead. The other 13 VINs, including every Ford, Peugeot, Volvo, Mazda and Tesla in the sample, came back as a clear NOT_FOUND rather than a guess. parts_catalog returns the car's OEM catalogue structure: groups, subgroups and assemblies (229 on a Toyota Corolla, 744 on an Opel Insignia, 1,510 on a VW Golf), each with the maker's applicability codes and a diagram thumbnail, filterable by words such as brake or water pump, in 32 languages. Part numbers are not included. Each decode names the matching Autodoc maker, so the next call can be the Autodoc API for the parts that fit that car, with prices. No 7zap account is needed: one ReefAPI key and the standard { ok, data, meta, error } envelope.
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.
| Field | Hyundai Tucson, TMAJC81BGPJ324179 | Opel Insignia, W0LGT8GS1F1095696 | VW Golf, WVWZZZAUZLW053403 |
|---|---|---|---|
| make, model | Hyundai, Tucson NX4 | Opel, Insignia A | Volkswagen, Golf A7 Facelift |
| year | 2023 | 2015 | 2020 |
| engine | G32X (1600 cc, petrol) | LHV (2000 cc, diesel) | null: VW-group catalogues give no engine here |
| transmission | M33W (DCT, 7 speed, 2WD) | MYJ (manual, 6 speed) | null |
| body | WAGON - 5DR 5P | null | AU (body code) |
| market | EUR | null | null |
| production_date / production_window | 2023-02-27 | 2015-07-14 | window 2019-07-01 to 2020-08-31 |
| generation_years | 2020 to 2024 | 2009 to 2017 | 2017 to 2027 |
| specification[] | 14 facts, including engine number and transmission number | 4 facts | 4 facts |
| autodoc.maker | hyundai | opel | vw |
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.
Real request and response JSON
Captured from the indexed primary action, vin_decode, on .
{
"method": "POST",
"url": "https://api.reefapi.com/7zap/v1/vin_decode",
"headers": {
"x-api-key": "$REEF_KEY",
"content-type": "application/json"
},
"body": {
"vin": "TMAJC81BGPJ324179"
}
}{
"ok": true,
"meta": {
"api": "7zap",
"endpoint": "vin_decode",
"mode": "live",
"latency_ms": 2095.5,
"record_count": 1,
"bytes": 152871,
"cache_hit": false,
"details_status": "ok",
"upstream_requests": 2,
"charged_credits": 2,
"version": "1.0.0",
"request_id": "fffd315a8b9c4f5b",
"queue_ms": 3.4,
"fetched_at": "2026-11-19T10:12:02.471Z"
},
"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)."
}
}
}What the 7zap API does
| Action | Description | Concrete use case | Key params |
|---|---|---|---|
| vin_decode | Decode a 17-character VIN with 7zap's OEM catalogue: make, model series, generation, year, a picture of the generation, and — from the maker's own parts catalogue — the factory configuration where 7zap has it: engine (code, size, fuel), gearbox, body, drive, steering, market, trim, production date or production window, and for some makes the engine and gearbox serial numbers and paint colour. Also returns 7zap's catalogue link for this exact car, the `vehicle_code` that `parts_catalog` takes, and an `autodoc` block (Autodoc maker slug + the next calls) to go on to parts with prices. Measured 2026-11-19 on 34 real EU VINs from car listings: 21 decoded, make and model right on all 21 (VW, Audi, BMW, Skoda, Seat, Cupra, Renault, Hyundai, Kia, Toyota, Nissan, Opel, Mercedes, Citroen, Fiat, Dacia); 13 came back NOT_FOUND (Ford 0/2, Peugeot 0/2, Volvo 0/2, Mazda, Tesla, and some models of other makes). How detailed the factory facts are depends on the make: Toyota, Nissan, Hyundai, Kia, Opel, Renault, Dacia, Citroen and BMW include the engine (12 of the 21); VW-group cars carry body, year and production window. `year` is 7zap's; where 7zap derives it from the generation range `year_is_estimate` is true. | Pricing teams call vin_decode to get decode a 17-character VIN with 7zap's OEM catalogue. | vin, language, details |
| parts_catalog | The OEM parts-catalogue structure of one car, as 7zap shows it: top-level groups (Engine, Transmission, Chassis, Body, Interior, Electrical, Accessories, Maintenance) → subgroups → assemblies, each assembly with its code, name, the maker's applicability codes (engine / equipment codes it applies to) and a diagram thumbnail. 130-1 500 assemblies per car. Give a `vin`, or the `vehicle_code` + `make` from `vin_decode`; narrow with `query` (words in the assembly name) or `group`. Part numbers are NOT included: 7zap shows OE numbers only to signed-in members (logged out they are masked), so this action returns none rather than masked ones. | Marketplace operators call parts_catalog to get the OEM parts-catalogue structure of one car, as 7zap shows it. | vin, vehicle_code, make, query, group, ... |
Call vin_decode from your stack
curl -X POST https://api.reefapi.com/7zap/v1/vin_decode \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"vin":"TMAJC81BGPJ324179"}'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": "TMAJC81BGPJ324179"
},
timeout=90,
)
print(r.json()["data"])const res = await fetch("https://api.reefapi.com/7zap/v1/vin_decode", {
method: "POST",
headers: {
"x-api-key": process.env.REEF_KEY,
"content-type": "application/json",
},
body: JSON.stringify({
"vin": "TMAJC81BGPJ324179"
}),
});
const { ok, data, meta, error } = await res.json();Ask your MCP-connected assistant: call reefapi.7zap.vin_decode with {"vin":"TMAJC81BGPJ324179"}.Who uses this API and why
- Parts shops: the customer types a VIN and sees the exact generation, engine code and gearbox before choosing a part.
- VIN to parts with prices: decode with 7zap, then list the Autodoc parts that fit that engine variant.
- Used-car listing checks: compare the seller's model, year and engine with what the maker's catalogue says for the VIN.
- Garage and fleet software: store engine code, gearbox and production date per vehicle from the VIN alone.
- Catalogue navigation: one car's OEM groups and assemblies in 32 languages, to build a which-part-is-this picker.
Questions developers ask before integrating
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.