Use cases of the tapinomahub APIsAll articles

Use cases of the tapinomahub APIs

Reading endpoints individually explains what a call does. This overview explains which calls together complete a task — and on which of the four surfaces your task sits.

Published: 2026-09-12Reading time: 6 mintapinomahub API & workflows
API & processesAPIVINOE numberVehicle dataMarketplacesPricing & valuation

An endpoint list answers the question “what can this call do”. It does not answer the question a business actually has: “how do I get this task done”. The use cases on this page therefore start from the task and name the calls that complete it together — each with its prerequisites, a billing note and its limits.

Four surfaces, one platform: where your task belongsYour task — Each surface has its own contract and its own maturity. The choice follows the task, not taste. 1. Data and images — Hub (GET /parts/oe/{oeNumber}): Vehicle, part, document, image: the productive surface 2. Answering customers — sales agent (POST /agent/conversations): Marketplace, mailbox and website, with handover to a human. Run as a pilot. 3. Selling and reconciling — Commerce (GET /commerce/v1/capabilities): Catalogue, inventory, order, fee. Preview without productive channel changes. 4. Keeping evidence — Compliance (POST /compliance/cases): Intake, certificate, treatment, material flow, authority. Documentation preview, not yet activated. The surfaces are not exclusive: for a recycler Hub and Compliance are relevant options, for a dealer Hub and Commerce.Your taskEach surface has its owncontract and its own maturity.The choice follows the task,not taste.Four surfaces, one platform: where your task belongsData and images — HubGET /parts/oe/{oeNumber}Vehicle, part, document, image: the productive surfaceAnswering customers — sales agentPOST /agent/conversationsMarketplace, mailbox and website, with handover to a human.Run as a pilot.Selling and reconciling — CommerceGET /commerce/v1/capabilitiesCatalogue, inventory, order, fee. Preview without productivechannel changes.Keeping evidence — CompliancePOST /compliance/casesIntake, certificate, treatment, material flow, authority.Documentation preview, not yet activated.The surfaces are not exclusive: for a recycler Hub and Compliance are relevant options, for a dealer Hub andCommerce.
Four surfaces with their own contract and their own maturity. The choice follows the task.

The four surfaces are not exclusive. For a recycler the Hub and Compliance are relevant options, for a parts dealer the Hub and Commerce, for a software vendor building for many businesses all four — each surface at its own maturity. Authoritative for every path named is the OpenAPI contract of the respective surface.

The four surfaces and their maturity

SurfaceMaturityUse cases
Hubproductive12
Sales agentpilot — entitlement required8
Commercepreview — no productive channel changes11
Compliancedocumentation preview — not yet activated9

All use cases

Use caseSurfaceRoles
Vehicle file from the registration document: intake, condition, listingHubDealership, Vehicle trading, Fleet and leasing
Checking recalls before a vehicle or part moves onHubVehicle trading, Workshop, Fleet and leasing, Parts trading
Damage file from calculation and photos: from PDF to structureHubExperts and insurers, Workshop, Vehicle trading
Does the part fit the vehicle? Checking the cart against the VINHubParts trading, Workshop, Platform and marketplace
Producing product images without running a photo studioHubParts trading, Platform and marketplace, Vehicle trading
A software vendor operates many businesses on one accessHubSoftware vendor, Platform and marketplace
Using the software vendor’s cost sponsorship — or deliberately notHubWorkshop, Vehicle recyclers, Dealership
End-of-life or not? From the image finding to a reasoned determinationHub + ComplianceVehicle recyclers, Vehicle trading, Experts and insurers
Buying a vehicle from abroad without having the document translatedHubVehicle trading, Vehicle recyclers, Fleet and leasing
Goods-in: reading labels as deeply as the article needsHubParts trading, Vehicle recyclers
Showing the damage on a body part before it is removedHubVehicle recyclers, Parts trading
The sales agent answers in the widget on your own websiteSales agentParts trading, Vehicle trading, Platform and marketplace
Connecting marketplace and mailbox to the sales agentSales agentParts trading, Platform and marketplace, Vehicle trading
Instructing the agent and giving it a ceilingSales agentParts trading, Vehicle trading, Software vendor
When a colleague takes the conversation overSales agentParts trading, Vehicle trading, Workshop
Embedding the sales agent in your own chat or ticket softwareSales agentSoftware vendor, Platform and marketplace, Parts trading
Stopping the sales agent without losing a single messageSales agentParts trading, Vehicle trading, Software vendor
Buyers’ price offers: what the agent decided and what it did notSales agentParts trading, Vehicle trading
Taking over your helpdesk answers without the agent saying them uncheckedSales agentParts trading, Vehicle trading, Workshop
Connecting a sales channel without ending up with two writing systemsCommerceParts trading, Platform and marketplace, Software vendor
Running catalogue and inventory, reserving unique piecesCommerceParts trading, Vehicle recyclers, Platform and marketplace
From the incoming order to the reported shipmentCommerceParts trading, Vehicle trading, Software vendor
Cancellation, return and refund as one processCommerceParts trading, Vehicle trading
Setting prices, recomputing fees, establishing discrepanciesCommerceParts trading, Software vendor, Platform and marketplace
Transferring a catalogue as a file — with review notes before it is taken overCommerceParts trading, Vehicle trading, Software vendor
Inspecting a returned part and deciding what happens to itCommerceParts trading, Vehicle recyclers
Resolving and evidencing a discrepancy from the reconciliationCommerceParts trading, Software vendor, Platform and marketplace
Holding an ordered unique piece until the order is fulfilled or settledCommerceParts trading, Vehicle recyclers
Month-end close from documents rather than bank statementsCommerceParts trading, Vehicle trading, Software vendor
Taking in a vehicle and determining its legal statusComplianceVehicle recyclers, Dealership, Vehicle trading
The certificate of destruction from draft to deliveryComplianceVehicle recyclers
Preparing deregistration and submitting it to the authorityComplianceVehicle recyclers, Dealership
Treat, assess, reuse — every step with its evidenceComplianceVehicle recyclers, Parts trading
Material flows, transfers and an operating journal that closesComplianceVehicle recyclers
Passing a vehicle on as a used vehicle, not as end-of-lifeComplianceVehicle trading, Vehicle recyclers, Dealership
When a vehicle intake is not the normal caseComplianceVehicle recyclers
From the dismantling bay to the sale — release first, price secondCompliance + Hub + CommerceVehicle recyclers, Parts trading

If you do not yet know where to start

Where the binding statements live

Field lists, error codes and sample responses live in the OpenAPI contracts at docs.tapinomahub.com. The texts here explain the context; in case of doubt the contract governs.

Frequently asked

How does a use case differ from an endpoint article?

The endpoint article describes one call. A use case describes a task needing several calls and justifies the order — including the stages people like to skip.

Can I use several surfaces at once?

The surfaces are not exclusive, but they have separate contracts and their own maturity; for a recycler Hub and Compliance are relevant options.

Are all surfaces available productively?

The Hub runs productively; Compliance is a documentation preview whose endpoints are not yet activated on the target server. The sales agent is run as a pilot and needs an entitlement. Commerce is a preview and performs no productive channel changes and no fee collection.