Partner integrationmobile.de Seller API compatible format

Automedia Inventory REST API

Integration guide for partners receiving Automedia's vehicle inventory feed.

What this is: Automedia operates a data export ("the Interface") that replicates the data structure and field format of the mobile.de Seller API so that systems already built against that format can receive Automedia inventory data without changes. This page documents only the surface Automedia's exporter actually uses. For every request format, field definition, validation rule and response code, the mobile.de Seller API documentation remains authoritative.

Naming and trademarks

This integration is described here as the Automedia Inventory REST API. It is an Automedia product, provided independently and without any commission from mobile.de. It is not a mobile.de product, and using it does not create any relationship with mobile.de. The interface is compatible with the mobile.de Seller API data format for interoperability purposes only.

Transport and auth

Authentication follows the same principles as the mobile.de Seller API (see mobile.de's Authentication and authorization documentation):

HTTPS; HTTP Basic auth on every request.
Media type application/vnd.de.mobile.api+json (Accept and, for JSON bodies, Content-Type).
Automedia provides a base URL and issues Basic-auth credentials for the exporter.

How onboarding works

This service is the Automedia Inventory REST API: an inventory feed delivered through an endpoint that speaks the mobile.de Seller API schema. It is not the mobile.de Seller API itself; it only uses the same request format.

An exporter (the Automedia system that sends inventory) pushes a dealer's vehicles to your endpoint using exactly the same requests it would send to mobile.de. To onboard, the exporter is simply configured with your endpoint's base URL and Basic-auth credentials, nothing else changes. Your endpoint must therefore accept the mobile.de Seller API request format as documented by mobile.de; this page defines only the surface that is actually exercised.

Endpoints used

All exactly as specified by mobile.de (linked). Your endpoint must implement these:

Method and path	Purpose	mobile.de reference
`POST /seller-api/sellers/{sellerId}/ads`	Create ad	Create a new ad
`PUT /seller-api/sellers/{sellerId}/ads/{adId}`	Update ad (full replace)	Update an ad
`DELETE /seller-api/sellers/{sellerId}/ads/{adId}`	Delete ad	Delete an ad
`GET /seller-api/sellers/{sellerId}/ads/{adId}`	Read ad (status verify)	Ad resource
`PUT /seller-api/sellers/{sellerId}/ads/{adId}/images`	Replace full image set	Images
`PUT /seller-api/sellers/{sellerId}/ads/{adId}/leasing`	Upsert leasing offer	Leasing
`DELETE /seller-api/sellers/{sellerId}/ads/{adId}/leasing`	Remove leasing offer	Leasing
`GET /seller-api/sellers/{sellerId}/ads/quality-check?adIds=…`	Batch existence and status check (reconciliation)	Quality check

Optional Analytics endpoints. The exporter tolerates 404/empty if not implemented: GET /insights-api/performance-comparison/sellers/{sellerId} and GET /insights-api/sales-probability/sellers/{sellerId}.

Behaviours the integration depends on

These are mobile.de behaviours (see the linked sections) that the exporter relies on. Make sure your implementation matches them:

Create returns the ad id in the Location header (201, or 303 for an idempotent duplicate). The exporter reads the id from the last path segment of Location; a create without a usable Location is treated as failed. See Avoiding duplicated ads.
Idempotency: the exporter sends X-Mobile-Insertion-Request-Id on create; a retry with the same key must return the existing ad, not a duplicate. See Idempotent methods.
Update is a full replace. Omitted fields are treated as unset.
404 on update: the exporter recreates the ad via POST.
404 on delete (ad or leasing) is treated as success (idempotent).
Images: multipart/form-data, one part per image under field name images, in order (first is the title image); a PUT replaces the whole set.
Quality-check absence means gone: the response must include entries only for ad ids that still exist; ids omitted from the response are treated as deleted. This drives reconciliation.
Validation errors: non-2xx with mobile.de's error body ({ "errors": [ { "key", "args" } ] }). On a failed create/update the exporter removes the field named by the error key and retries once, so meaningful error keys are important. See Error handling and data validation.

Per-vehicle call sequence

Upsert the ad: PUT .../ads/{adId} if an id is held (on 404, create), else POST .../ads and read the id from Location.
Upload images: PUT .../ads/{adId}/images (full, ordered set).
Sync leasing: PUT .../leasing when applicable, else DELETE .../leasing.

A vehicle that has left the inventory triggers DELETE .../ads/{adId}. Reconciliation periodically calls quality-check in batches (up to 500 ad ids per request).

Ad data

Implement the full mobile.de Ad schema and accept any attribute it defines, see Ad schema, Data format reference, and the reference-data value catalogs (makes, models, categories, fuels, gearboxes, colours, emission classes, features) under the Search API and refdata endpoints.

The exporter populates a broad, data-dependent subset. Only attributes that have a value for a given vehicle are sent, so the set varies by vehicle and by dealer. Because of that, do not assume a fixed field set: treat every mobile.de Ad attribute as possible, and do not hard-fail on attributes you don't use.

Non-standard fields

The exporter may additionally send fields that are not part of the mobile.de Ad schema:

Field	Handling required
`amSerialequipment`	Vendor extension text field. Your endpoint can safely ignore it, but must not reject the request because of it.
`campaignIds`	A list of campaign identifiers associated with the ad. Your endpoint must accept and process this attribute.

Legal notice

Trademark disclaimer "mobile.de" and "Seller-API" are trademarks of mobile.de GmbH and/or its affiliated companies. The Automedia Inventory REST API described on this page is developed, operated, and provided independently by Automedia Marketing und Medienservice für den Kfz-Handel GmbH. It is not commissioned by, endorsed by, or affiliated with mobile.de GmbH. References to the mobile.de Seller API on this page describe data-format compatibility only; they do not imply any partnership, sponsorship, or official connection with mobile.de.

This document is provided to partners as the technical documentation referenced in the interface annex to the applicable SaaS agreement between Automedia and the partner. In case of any discrepancy, the terms of that agreement take precedence.

Contact

Provider

Automedia Marketing und Medienservice für den Kfz-Handel GmbH

Integration support

integration@automedia.de

Imprint