What you get back
You receive a structured parts list with match quality, stable tapinomahub GenArt, VDI 4081 mappings and available OE numbers; variants and gaps remain visible as specific review tasks.
A typical day-to-day use case
A recycler opens the donor vehicle in the dismantling system. The VIN-based parts list defines what should be checked, removed and created in stock.
The tangible business value
Information that would otherwise need to be searched, transferred and checked repeatedly is available consistently. This shortens processing time and reduces the risk of poor decisions.
- Saves search, capture or waiting time because the task starts and finishes inside the familiar system.
- Reduces transfer and matching errors because information is not retyped or reconciled across separate lists.
- Improves the commercial use of existing data by making offers complete, discoverable and transparent sooner.
Who benefits most
| Area of use | The practical advantage |
|---|---|
| New, remanufactured and used parts trading | Improves matching, product data and multichannel sales for new, remanufactured and used parts. |
| Vehicle recyclers | Connects vehicle intake, dismantling, part capture and stock marketing in one consistent data flow. |
| Workshops | Reduces manual transfer and mismatches between the vehicle, work order and required part. |
| ERP, DMS, shop and software providers | Embeds the capability in the system of record through an API and processes results without another manual step. |
How the endpoint fits your workflow
The endpoint handles one clear task and passes its result straight to the next step.
- Your system sends the available number or information to tapinomahub.
- tapinomahub matches it against the appropriate enabled data sources.
- The result is reviewed and used in the next step without retyping.
What you actually get back
You send a vehicle identification number and receive neither finished shop products nor a pricing decision. You receive the vehicle-specific data basis for those decisions. Your system can identify relevant assemblies, verify OE references and connect the results to its own inventory of new, used or remanufactured parts.
| Response | Operational value |
|---|---|
| Vehicle-specific part candidates | Narrows the search to the identified vehicle and replaces every model variant with a reviewable working set. |
tapiGenArt for each position | Maps results to a stable tapinomahub part class so the shop, ERP, workshop and warehouse use the same assembly language. |
vdi for each position | Contains confirmed full VDI 4081 codes. Without a valid mapping, the required field remains present as []. |
| OE number where available | Connects the result to product master data, supersession chains, aftermarket references, prices and internal inventory. A missing number stays visible and must not be invented. |
| Match quality, categories and variants | Shows which positions can continue automatically and where technical or physical review is still required. |
202 Accepted, Location and Retry-After | A background job handles longer searches. Your system waits in a controlled way and retrieves the result from the supplied status URL instead of repeating the request blindly. |
Three realistic operating cases
| User story | How the process works | Tangible value |
|---|---|---|
| B2C and B2B parts finder: As a shop operator, I want to use the VIN in search or checkout so buyers do not have to guess between unclear variants. | Identify the vehicle, retrieve the parts basis, confirm usable OE numbers through GET /parts/oe/{oeNumber} and map them to new, used or remanufactured inventory. Before purchase, POST /vin/cart-check can additionally check the cart. | Fewer avoidable mismatches, fewer fitment questions and a shorter path from vehicle to purchasable offer. Measure the effect through compatibility-related returns and conversion. |
| Workshop estimate: As a service adviser, I want to find the relevant part family from the VIN so a quotation does not start with manual transfers from several catalogues. | After the VIN match, the workshop selects the repair scope, confirms the OE basis and adds prices, labour, fluids and taxes from its own systems. | Fewer catalogue changes and typing errors, faster preparation of a reviewable quotation and one consistent vehicle record. The API replaces neither diagnosis nor the technician’s decision. |
| Smart pick list for dismantling: As a dismantling manager, I want to know before the lift which parts of the donor vehicle may be commercially worthwhile. | Combine the parts basis with GET /vin/{vin}/economic-evaluation, inventory, sales data and removal time. At removal, physically confirm the OE identifier, condition and part actually installed. | Prioritised rather than blanket dismantling, less labour spent on slow-moving parts and earlier digital capture. The endpoint alone knows neither condition nor achievable selling price. |
From API result to a reliable business process
- Identify the vehicle with
GET /vin/{vin}/vehicle. If the data provider requires approval in the tapinoma interface, complete the documented redirect process first. - Retrieve the parts basis with
GET /vin/{vin}/parts. A provider already selected belongs to the vehicle context and should not be overwritten inconsistently. - For
202 Accepted, store the suppliedLocation, respectRetry-Afterand pollGET /vin/parts/jobs/{jobId}until completion. - Evaluate match quality, missing categories and variants. Ambiguous positions go to targeted review instead of automatically reaching sale or installation.
- Confirm available OE numbers through
GET /parts/oe/{oeNumber}and add supersession chains or aftermarket references where needed. - Map confirmed references to your product master. Depending on the goal, continue with cart checking, pricing, workshop quotation or economic evaluation.
- Before binding approval, include real condition: modifications, previous repairs, labels, part photos and physical markings may supplement or correct the data basis.
Measure the economics honestly
Useful metrics: VIN coverage, successfully completed jobs, positions with a usable OE number, manual review rate, time to quotation, fitment-related support cases and returns, conversion and reasons for conflicting matches. Establish a baseline before rollout and compare the same periods and product ranges afterwards.
When it is time to implement
Fields, examples, possible responses and prices are available in the API documentation for GET /vin/{vin}/parts.
Sources and legal references
Frequently asked
What do I get back from this endpoint?
You receive a structured parts list with match quality, stable tapinomahub GenArt, VDI 4081 mappings and available OE numbers; variants and gaps remain visible as specific review tasks.
Who benefits most from this endpoint?
New, remanufactured and used parts trading, Vehicle recyclers, Workshops, ERP, DMS, shop and software providers.
Where can I find the implementation details?
The directly linked tapinomahub API documentation contains fields, examples, possible responses and prices.