What you get back
You receive a title, description and equipment highlights in German, English or French, together with transparent indicators for data coverage and possible truncation.
A typical day-to-day use case
After appraisal, the remarketing employee selects “Create listing”. The verified data becomes a complete text that only needs editorial approval.
The tangible business value
Images, documents or identifiers become a practical working basis. Your team saves capture time, works more consistently and can focus on the business decision.
- Saves search, capture or waiting time because the task starts and finishes inside the familiar system.
- Improves the commercial use of existing data by making offers complete, discoverable and transparent sooner.
Who benefits most
| Area of use | The practical advantage |
|---|---|
| Vehicle trading | Speeds up intake, data validation and remarketing without creating a second vehicle record. |
| 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. |
| 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.
- An authorised image, document or existing identifier is submitted from the familiar system.
- tapinomahub detects, matches or prepares the required content.
- A team member reviews the result and approves it for records, stock, offers or sales.
What the listing engine actually returns
The call starts with a stable tapiId from a successfully completed VIN flow, not with an unbound raw VIN. tapinomahub turns the vehicle data documented for that reference into a marketplace-ready copy draft. Your DMS, ERP or portal then adds price, mileage, current condition, damage, photos, seller details and the mandatory fields of the target channel.
| Response | Operational value |
|---|---|
title | A compact listing title based on evidenced vehicle attributes, ready to become the starting point for a website, marketplace or B2B dossier. |
description | A readable vehicle description without invented equipment and without price, condition or value promises. |
highlights | Documented equipment is returned as individually reusable benefits for cards, lists or marketplace fields. |
documentedEquipmentCount | Shows how many equipment attributes are evidenced in the vehicle record. It is a control value, not a claim that the full factory specification is complete. |
truncated | Shows whether the draft was shortened. When true, an editor decides which evidenced details should be added separately. |
format, tapiId and language | Keep the vehicle reference, output format and language machine-readable so draft and approval remain connected to the right inventory record. |
Three realistic operating cases
| User story | How the process works | Tangible value |
|---|---|---|
| Vehicle retail: As an inventory coordinator, I want a complete first draft shortly after intake so a vehicle is not left unmarketed purely because of writing work. | Capture registration data, complete the VIN flow, store the tapiId, pass language and evidenced dealer notes, review the draft and then send it through an internal connector to mobile.de, the website or other channels. | Shorter time from a complete vehicle record to an approved listing, less copy and paste and fewer overlooked documented extras. Not zero seconds, but a measurably faster approval process. |
| Accident vehicle and salvage marketplace: As a remarketing manager, I want to combine a neutral vehicle and equipment basis with a separately evidenced damage record so bidders can assess opportunities and risks faster. | Compose Vehicle Listing supplies the evidenced vehicle copy. Damage, condition and photos are added separately from a return report, appraisal or POST /vision/condition-report and receive professional approval before publication. | A more consistent B2B dossier, fewer equipment questions and better comparability. Higher bids are a possible outcome, not a guaranteed effect. |
| Fleet and leasing: As a fleet manager, I want to prepare many returns with the same logic so quality does not depend on the individual editor. | Use the same flow, selected language and a separate Idempotency-Key for each tapiId. Brand voice, marketplace fields, prices and return condition are then added through templates and approval rules. | More throughput without proportionally more copywriting, more consistent drafts and fewer transfer errors. Brand compliance comes from the downstream template, not automatically from the endpoint. |
From vehicle to published advertisement
- Identify the vehicle through the documented VIN flow. If the selected provider requires browser approval, complete the redirect first and securely map the returned
tapiIdto the internal vehicle record. - Review documented vehicle data through
GET /vehicles/{tapiId}where needed. Current operational data such as mileage or selling price remains in its responsible source system. - Choose
language, the required quality level and no more than 500 characters of factualnotes. A dedicatedIdempotency-Keyprevents accidental duplicate execution; successful responses can be replayed with it for 24 hours. - Call
POST /vehicles/{tapiId}/listingand accept title, description, highlights,documentedEquipmentCountandtruncated. - Review missing or shortened content. Unevidenced equipment is not added; an unknown or foreign vehicle reference returns
404 vehicle_not_foundinstead of guessed copy. - Add price, mileage, current condition, damage, images, warranty information and other mandatory fields from approved systems. The endpoint deliberately does not create these claims.
- Validate the completed record against the target channel schema. The mobile.de Seller API can create and manage ads programmatically, but requires a separate connector and its own credentials.
- Publish only after editorial and professional approval, and record timestamp, version, target channel and later corrections in the vehicle record.
Measure time savings and quality reliably
Useful metrics: median time from complete vehicle record to publication, handling time per listing, first-pass approval, documented highlights, share of truncated=true, manual corrections, marketplace rejections, missing mandatory fields and time to first qualified enquiry. Evaluate selling price and stock days only for comparable vehicle groups and with other influencing factors.
Law and marketplace rules remain part of approval
For offers in Germany, section 5 UWG prohibits misleading statements about matters including material characteristics, availability and price. For consumer offers, the German Price Indication Ordinance requires clear, attributable total prices. Because Compose Vehicle Listing generates neither price nor condition, the downstream sales process must add and review these details from responsible sources. A marketplace may also impose its own mandatory fields and validation rules.
When it is time to implement
Fields, examples, possible responses and prices are available in the API documentation for POST /vehicles/{tapiId}/listing.
Sources and legal references
Frequently asked
What do I get back from this endpoint?
You receive a title, description and equipment highlights in German, English or French, together with transparent indicators for data coverage and possible truncation.
Who benefits most from this endpoint?
Vehicle trading, Vehicle recyclers, Workshops, Fleets, leasing and remarketing, 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.