The tapinomahub API connects vehicle and parts data, document recognition, image workflows and platform administration with existing ERP, DMS, inventory and shop systems. This section explains every active public endpoint once and shows where it belongs in the overall workflow.
Knowledge pages and API documentation serve different purposes
The knowledge section answers why a capability exists, where it helps and who benefits. The API documentation defines parameters, responses and status codes. If technical details differ, the published documentation is always authoritative.
| Area | Endpoints | General purpose |
|---|---|---|
| System | 1 | System endpoints provide a clear basis for availability checks, monitoring and controlled error handling. |
| VIN & vehicle matching | 6 | VIN endpoints establish a shared vehicle context for identification, parts matching, cart checks and economic evaluation. |
| Vehicle record | 3 | Vehicle endpoints combine intake, technical data and marketing around a controlled tapiId. |
| Parts & OE | 4 | Parts endpoints normalise OE identifiers and add reliable references for procurement, stock, sales and compatibility checks. |
| Intelligence | 9 | Intelligence endpoints combine market and sales data into explainable pricing, demand and economic signals for parts and vehicles. |
| Scanner & documents | 8 | Scanner endpoints turn authorised documents, labels and vehicle images into structured fields that systems can process. |
| Vision & image workflows | 12 | Vision endpoints structure visible conditions and prepare vehicle or part images for review, records and marketing. |
| Recalls | 2 | Recall endpoints match vehicles or parts lists against published safety measures from official registers. |
| Translation | 1 | Translation endpoints make individual part names reusable across multilingual catalogues and sales channels. |
| VDI catalogue | 1 | VDI endpoints provide a versioned catalogue for consistent parts and used-parts data and expose its revision in machine-readable form. |
| Platform administration | 15 | Client Admin endpoints control tenants, keys, entitlements, usage, limits and transparent sponsored billing for partner networks. |
How every endpoint profile is structured
- A clear service description rather than merely repeating the path.
- General commercial and operational value.
- Separate context for the target groups that actually benefit.
- A concrete flow from input and call through review and system handover.
- Limitations, permissions and a direct link to the technical contract.
From an individual endpoint to a complete workflow
- Capture the input: VIN, document, image, OE number or administrative request.
- Validate identity and permission before paid or sensitive processing starts.
- Match, analyse or transform data while keeping uncertainty visible.
- Approve the result professionally and transfer it to the system of record with an audit trail.
- Track downstream processes, asynchronous jobs, usage and errors under controlled rules.
Who this section is for
| Target group | Typical value |
|---|---|
| Vehicle trading | Speeds up intake, data validation and remarketing without creating a second vehicle record. |
| 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. |
| Fleets, leasing and remarketing | Standardises vehicle checks, records and handovers across locations and service providers. |
| Assessors and insurers | Structures incoming documents and visual findings for traceable assessment and claims processes. |
| ERP, DMS, shop and software providers | Embeds the capability in the system of record through an API and processes results without another manual step. |
| Platform and partner networks | Makes permissions, usage and sponsored billing manageable across connected businesses. |
Four useful starting points
- Identify a vehicle: Compare vehicle data by VIN.
- Match an OE part: Compare OE part name, fitment, reference family and replacement chain.
- Read a registration document: Extract a vehicle registration document.
- Structure vehicle condition: Create a vehicle condition report from images.