Table of Contents

Version 2025-11-19

Basics

Introduction

Overview

The Lead API is an interface to send and receive lead insights with mobile.de. It enables API users to query and update their leads reliably.

The API is available at this base URL:

https://services.mobile.de

Prerequisites

Lead API access can be granted to Transfer Service Providers and Lead Management System partners registered with mobile.de.

Support for the development process and maintenance is limited:

The examples in this documentation are provided as guidelines to help your development. While we cannot offer direct support for specific programming languages or custom scripts, we ensure our API adheres to standard conventions for easy integration.

Test Account

A test environment can be provided. Please send the following information to service@team.mobile.de:

  • The mobile.de customer number and company name

  • A request for Lead API activation

  • A request to get a new mobile.de dealer in our sandbox environment

  • The name, email and telephone number of the person who handles contractual issues for the requesting company

  • The name, email and telephone number of the person who handles technical issues for the requesting company.

For more details, see the Quick Start section.

Lead API Concepts

API User / Transfer Service Provider

An API user is the entity that has an API account and uses that account to post ads for one or more sellers (which are linked to that account) to the API. Usually the API user is a technical partner which manages ads for a larger number of sellers.

Individual Dealer

A dealer is able to use the API like a TSP (Transfer Service Provider) but only for their dealer account.

Lead

A lead represents "qualified intent" of a buyer’s interest in a vehicle. This describes the potential buyer’s expressed interest in a vehicle, indicating they wish to communicate with the seller.

Lead Event

A lead event documents a specific change on a given lead. One lead can have many lead events, ordered by time. Example: A lead lead-1234 has three lead events attached to it: event-3, event-2 and event-1, ordered by their recency.

Lead events are of a specific type, encapsulating specific data points of it. At the time of writing, lead events can be of type: MessagingLeadSubmitted and BuyerReplied.

MessagingLeadSubmitted Event

This event occurs when a potential buyer contacts a dealer via mobile.de’s contact form. It encapsulates the contact information of the potential buyer, vehicle information, the user’s message and the source system. A detailed view of the content can be seen in Resources Reference.

BuyerReplied Event

This event occurs when a potential buyer replies to an existing lead. The event itself contains only the content of the new reply. A detailed view of the content can be seen in Resources Reference.

MessagingLeadResubmitted Event

This event occurs when a potential buyer submits the mobile.de contact form on a listing where a conversation between this buyer and the seller already exists. This is an edge case where users intend to use to update their contact information.

Technically, the resubmission is added as another reply to the existing conversation between the buyer and the seller, but can contain contact information changes. It encapsulates the contact information of the potential buyer, vehicle information and the user’s message. A detailed view of the content can be seen in Resources Reference.

BuyerSearchBehaviourAdded

The BuyerSearchBehaviourAdded event provides insights into the user’s search behaviour on the platform. It is added to a lead after it has been initially submitted.

The event is present if the user has given their consent to share their data and there are sufficient data points available.

Lead Status

The lead status indicates the current state of a lead, whether it is ongoing or resolved and how. Each new lead will have the status IN_PROGRESS and can transit from any status to another.

Example: SOLD signals the lead resulted in the purchase of the vehicle.

At the time of writing, the lead status can be any of IN_PROGRESS, SOLD, NOT_INTERESTED, SPAM. More options might arrive in the near future.

Cursor

A cursor is like a bookmark that keeps track of position in a long list of data, such as database entries. When loading data in chunks, for example, page by page, the cursor helps continue from the exact spot where processing left off.

It’s an opaque string that gets passed back to the system to get the next set of results.

Access and Testing

Authentication and Authorization

The API is available at this base URL:

https://services.sandbox.mobile.de

The user must be authenticated with a username and password using the HTTP basic authentication scheme. For detailed information on HTTP basic authentication see

During the activation process the Customer Support will provide you with instructions how to get the access credentials. The credentials are unique for each API user and do not depend on sellers or ads.

Getting a Test Account

The API test account can be requested by email to service@team.mobile.de. The email should state that you request an API User account for the API Sandbox environment with access to the Lead API.

Quick Start

Make a sample REST API call to the testing environment of mobile.de.

Preparation

cURL: This example uses cURL, an open source command line tool, to make http requests. On Mac or Linux systems cURL is usually pre-installed, Windows users can find cURL at https://curl.haxx.se.

For this example, you require read access for the Lead API in the API Sandbox environment. Please refer to the Getting a Test Account to get access to the testing environment.

Further Readings:

Make a Test Call

To verify that the service is running and your credentials are correct you can make the following request. You may find your mobileSellerId in the account details you received.

Request
curl --request GET \
  --url https://services.sandbox.mobile.de/lead-api/status \
  # The Basic string consists of username:password, encoded as base64.
  --header 'authorization: Basic dGVzdC1stttWWW123==' \
Response
{
  "status": "UP"
}

Testing API Functionalities

As part of the Lead API, we offer external partners the Lead API Sandbox to test the integration using sample data. Test data can currently be generated for the following Lead Events:

  • MessagingLeadSubmitted

  • BuyerReplied

  • MessagingLeadResubmitted

In terms of content, the test data such as messages, vehicle information, and information about potential buyers are currently static, except timestamps and dates.

MessagingLeadSubmitted Event

This endpoint generates a new lead for a specific dealer with an initial message.

Endpoint
POST /lead-api/sellers/{mobileSellerId}/sandbox/initial-submission
Parameters
Name Location Type Description

mobileSellerId

path

string

ID of the dealer account under management
cURL Example
curl 'https://services.sandbox.mobile.de/lead-api/status' \
  -H 'Authorization: Basic dGVzdC1stttWWW123==' # Base64 encoded string

BuyerRepliedEvent

This endpoint generates a buyer’s response for a specific dealer and lead. The lead must already exist (through an MessagingLeadSubmitted event).

Endpoint
POST /lead-api/sellers/{mobileSellerId}/sandbox/buyer-reply
Parameters
Name In Type Description

mobileSellerId

path

string

ID of the dealer account under management

leadId

query

string

ID of the Lead
cURL Example
curl -X POST "https://services.sandbox.mobile.de/lead-api/sellers/123456/sandbox/buyer-reply?leadId=LEAD123" \
     -H 'Authorization: Basic dGVzdC1stttWWW123==' # Base64 encoded string
API Response

Upon successful execution, both endpoints return HTTP status code 201 (Created). The response contains a JSON object in the following format:

Name Type Description

eventId

string

ID of the generated event

leadId

string

ID of the lead

MessagingLeadResubmitted Event

This endpoint generates a resubmission on an existing lead for a specific dealer.

Endpoint
POST /lead-api/sellers/{mobileSellerId}/sandbox/resubmission
Parameters
Name In Type Description

mobileSellerId

path

string

ID of the dealer account under management

leadId

query

string

ID of the Lead
cURL Example
curl -X POST "https://services.sandbox.mobile.de/lead-api/sellers/123456/sandbox/resubmission?leadId=LEAD123" \
     -H 'Authorization: Basic dGVzdC1stttWWW123==' # Base64 encoded string

BuyerSearchBehaviourAdded Event

This endpoint generates an event with buyer search behaviour on an existing lead for a specific dealer.

Endpoint
POST /lead-api/sellers/{mobileSellerId}/sandbox/buyer-search-behaviour
Parameters
Name In Type Description

mobileSellerId

path

string

ID of the dealer account under management

leadId

query

string

ID of the Lead
cURL Example
curl -X POST "https://services.sandbox.mobile.de/lead-api/sellers/123456/sandbox/resubmission?leadId=LEAD123" \
     -H 'Authorization: Basic dGVzdC1stttWWW123==' # Base64 encoded string

Resources Reference

This section contains a detailed description of all endpoints provided by the Lead API.

Please note that the endpoints below are available on the following base url:

https://services.mobile.de

Please refer to the Access and Testing section for more information on how to access the api and the test environment.

Name

Method

Endpoint

Comment

Get lead updates for a dealer

GET

/lead-api/sellers/:mobileSellerId/events?cursor=:cursor

A new cursor will always be returned as long as there are leads left for pagination.

Update Lead Status of a lead

POST

/lead-api/sellers/:mobileSellerId/leads/:leadId/status

You may provide a timestamp indicating when the lead status change actually occurred.

Get lead updates for a dealer

GET /lead-api/sellers/:mobileSellerId/events?cursor=:cursor

Provides a list of leads associated with the given mobileSellerId. The response contains a list of leads and a nextCursor, in case there are newer leads that were not part of the response.

If a cursor is provided, only the lead events that occurred after this cursor will be returned.

If there are no leads after the provided cursor, events will be empty.

If no cursor is provided, the endpoint will return the most recent leads.

Parameters

Parameter Explanation

mobileSellerId

Unique identifier of the seller on mobile.de.

cursor

Unique identifier to allow fetching data from a specific lead onwards
HTTP/REST Specifics
Request
GET /lead-api/sellers/12/events?cursor=MjAyNC0wMS0wMVQxMjowMDowMFo6zLTk1YWItNzhhZC04YWVkLTc2ZWUxNTY3YWEwMw
Host: services.mobile.de
Response
HTTP/1.1 200 OK

{
  "version": "2025-04-16",
  "traceId": "tx-id-1",
  "nextCursor": "MjAyNC0wMS0wMVQxMjowMDowMFo6zLTk4YWVkLTc2ZWUYWEwMw==",
  "events": [
{
      "occurredAt": "2025-06-30T14:18:36+02:00",
      "eventId": "0197c0c6-6231-7cad-96ab-25ef2a24f1ce",
      "eventType": "MessagingLeadResubmitted",
      "leadId": "lead-2",
      "data": {
        "message": {
          "text": "Hi there, please contact me via this phone number instead."
        },
        "potentialBuyer": {
          "name": "Maria Mustermann",
          "firstName": "Maria",
          "lastName": "Mustermann",
          "email": "maria@test.com",
          "phone": {
            "internationalPrefix": 49,
            "number": "123456789"
          },
          "buyerIdentifier": "ed84c73ac1dd7e062c71df6ec05a315265b12dfd6d0"
        },
        "source": "MOBILE",
        "vehicle": {
          "mobileAdId": "1241451",
          "make": "BMW",
          "model": "i3",
          "conditionType": "USED",
          "type": "PKW",
          "customerNumber": "154152",
          "internalNumber": "1234",
          "firstRegistration": "2022-11",
          "mileage": 144022,
          "price": "13000"
        }
      }
    },
    {
      "occurredAt": "2025-06-30T12:18:36.209Z",
      "eventId": "0197c0c6-6231-7cad-96ab-25ef2a24f1cf",
      "eventType": "BuyerReplied",
      "leadId": "lead-1",
      "data": {
        "message": {
          "text": "Hi there, please tell me more"
        },
        "potentialBuyer": {},
        "source": "MOBILE"
      }
    },
    {
      "occurredAt": "2025-06-30T14:18:36+02:00",
      "eventId": "0197c0c6-6231-7cad-96ab-25ef2a24f1ce",
      "eventType": "MessagingLeadSubmitted",
      "leadId": "lead-2",
      "data": {
        "message": {
          "text": "Hi there, this is an initial submission"
        },
        "potentialBuyer": {
          "name": "Maria Mustermann",
          "firstName": "Maria",
          "lastName": "Mustermann",
          "email": "maria@test.com",
          "phone": {
            "internationalPrefix": 49,
            "number": "1823953021"
          },
          "buyerIdentifier": "ed84c73ac1dd7e062c71df6ec05a315265b12dfd6d0"
        },
        "source": "MOBILE",
        "vehicle": {
          "mobileAdId": "1241451",
          "make": "BMW",
          "model": "i3",
          "conditionType": "USED",
          "type": "PKW",
          "customerNumber": "154152",
          "internalNumber": "1234",
          "firstRegistration": "2022-11",
          "mileage": 144022,
          "price": "13000"
        }
      }
    },
    {
      "occurredAt": "2025-06-30T15:30:22+02:00",
      "eventId": "0197c0c6-7845-8dbe-a7bc-36fg3b35g2df",
      "eventType": "BuyerSearchBehaviourAdded",
      "leadId": "lead-2",
      "data": {
        "makeModels": [
          {
            "make": "BMW",
            "model": "3 Series"
          },
          {
            "make": "Audi",
            "model": "A4"
          }
        ],
        "fuelTypes": [
          {
            "value": "DIESEL"
          },
          {
            "value": "HYBRID"
          }
        ],
        "gearTypes": [
          {
            "value": "AUTOMATIC_GEAR"
          }
        ],
        "mileage": {
          "max": 50000
        },
        "firstRegistration": {
          "min": "202301"
        }
      }
    }
  ],
  "warnings": []
}
Consuming lead updates from the beginning

To consume lead events from the beginning, a "zero cursor" ("0") can be used to start fetching lead events from the beginning.

Request
GET /lead-api/sellers/12/events?cursor=0
Host: services.mobile.de

The response will be the same as in the above snippet, but starting from the oldest retrievable lead event.

Update Lead Status of a lead

POST /lead-api/sellers/:mobileSellerId/leads/:leadId/status

Assigns a new status to the specific lead as part of the bidirectional data exchange with Mobile.de.

You may provide a timestamp indicating when the lead status change actually occurred in case of asynchronous communication. For debugging purposes a custom traceId may be sent additionally.

The endpoint does not return anything.

Parameters
Parameter Explanation

mobileSellerId

Unique identifier of the seller on the mobile.de platform.

leadId

Unique identifier of the lead.

newStatus

IN_PROGRESS, SOLD, NOT_INTERESTED, SPAM
HTTP/REST Specifics
Request
POST /lead-api/sellers/12/leads/47
Host: services.mobile.de

{
  "newStatus": "SOLD",
  "occurredAt": "2025-06-30T14:18:36Z",
  "traceId": "optional-caller-specific-trace-id-for-debugging",
{
Response
HTTP/1.1 204 No Content

Data Format Reference

Lead Events Response
Example JSON

For an example, see Get lead updates for a dealer

Properties
Field Type Required Description Example

version

string

Yes

Current version of the Lead API

2025-08-04-poc

traceId

string

Yes

Identifier to track the flow of the request inside the system

dbdb88b0-40e6-4229-9e72-05dc51ce38f0

nextCursor

string

Optional

Cursor to continue querying with

dXNlcjpXMDdRQ1JQQTQ=

warnings

list of strings

Optional

List of (possibly breaking) changes which the used API version is in conflict with. Contains a link to the corresponding entry inside the mobile.de changelog

https://services.mobile.de/manual/changelog.html#2025-02-11

events

See Lead Events

Yes

See Lead Events
Lead Events

The events list inside Lead Events Response is always present, but contains either:

Each of the events contains common properties , which are described inside Lead Event Head

Example JSON

For an example, see Get lead updates for a dealer

MessagingLeadSubmitted

Note: See also Lead Event Head for common properties.

Properties of data for MessagingLeadSubmitted event are:

Field Type

message

Message

potentialBuyer

PotentialBuyer

vehicle

Vehicle

source

Source
MessagingLeadResubmitted

Note: See also Lead Event Head for common properties.

Properties of data for MessagingLeadResubmitted event are:

Field Type

message

Message

potentialBuyer

PotentialBuyer

vehicle

Vehicle
BuyerReplied

Note: See also Lead Event Head for common properties.

Properties of data for BuyerReplied event are:

Field Type

message

Message
BuyerSearchBehaviourAdded

Note: See also Lead Event Head for common properties.

The BuyerSearchBehaviourAdded event provides insights into the buyer’s search behavior on mobile.de, allowing dealers to understand what the buyer is looking for beyond the specific vehicle they inquired about. This event will only be returned if there was a certain degree of user interaction recorded.

Properties of data for BuyerSearchBehaviourAdded event are:

Field Type

makeModels

List of MakeModelInsight

fuelTypes

List of Insight

gearTypes

List of Insight

mileage

Mileage (optional)

firstRegistration

FirstRegistration (optional)
Lead Event Head
Field Type Required Description Example

occurredAt

string

Required

Time when the lead was created in ISO 8601 format

2025-06-30T14:18:36+02:00

eventId

string

Required

The ID of the event

7776dacb-4db4-4cc5-88d9-b74c226c8c2a

eventType

EventType enum

Required

Type of the event (MessagingLeadSubmitted, BuyerReplied, MessagingLeadResubmitted, BuyerSearchBehaviourAdded)

MessagingLeadSubmitted

leadId

string

Required

The ID of the lead

84d6dcfd-4db4-4cc5-88d9-b74c226c8c2a
Potential Buyer
Example JSON
{
  "potentialBuyer": {
    "name": "Mathilda Mustermann",
    "firstName": "Mathilda",
    "lastName": "Mustermann",
    "email": "m.m@example.com",
    "phone": {
      "internationalPrefix": 49,
      "number": "1823953021"
    },
    "buyerIdentifier": "5c721fe9d951e5aafc634ed84c73ac1dd7e062c71df6ec05a315265b12dfd6d0",
    "testDrive": {
      "selected": true,
      "date": "2023-10-01",
      "time": "10:00"
    },
    "tradeIn": {
      "selected": true,
      "make": "Volkswagen",
      "model": "Golf",
      "firstRegistrationYear": 2015,
      "firstRegistrationMonth": "12",
      "mileage": 30000,
      "fuelType": "DIESEL",
      "transmission": "SEMIAUTOMATIC_GEAR",
      "power": 150,
      "powerUnit": "kW",
      "accidentDamaged": false,
      "numberOfPreviousOwners": 1,
      "exteriorColor": "Black",
      "doors": "TWO_OR_THREE",
      "category": "SmallCar",
      "trimLevel": "GLC 350e 4MATIC SUV",
      "vehicleIdentificationNumber": "1M8GDM9AXKP042788"
    },
    "delivery": {
      "selected": true,
      "city": "Berlin",
      "zipCode": "12345"
    },
    "financing": {
      "selected": true,
      "downPayment": 10000.0,
      "creditTerm": 48,
      "monthlyInstallment": 200.0
    },
    "leasing": {
      "selected": true,
      "contractTerm": 48,
      "downPayment": 10000.0,
      "grossRate": 200.0,
      "mileage": 20000
    }
  }
}
Properties
Field Type Required Description Example

name

string

Optional

Full name of the potential buyer

Mathilda Mustermann

firstName

string

Optional

First name of the potential buyer

Mathilda

lastName

string

Optional

Last name of the potential buyer

Mustermann

email

string

Optional

Email address of the potential buyer

m.m@example.com

phone.internationalPrefix

integer

Optional

International phone prefix

49

phone.number

string

Optional

Phone number without international prefix

1823953021

buyerIdentifier

string

Optional

Unique identifier for the buyer

5c721fe9d951e5aafc634ed84c73ac1dd7e062c71df6ec05a315265b12dfd6d0

testDrive

object

Optional

Test drive preferences

See Test Drive section

tradeIn

object

Optional

Trade-in vehicle details

See Trade In section

delivery

object

Optional

Delivery preferences

See Delivery section

financing

object

Optional

Financing details

See Financing section

leasing

object

Optional

Leasing details

See Leasing section
Test Drive
Field Type Required Description Example

selected

boolean

Optional

Indicates whether the user is interested in a test drive

true

date

string

Optional

Test drive date in YYYY-MM-DD format

2025-10-01
Trade In
Field Type Required Description Example

selected

boolean

Optional

Whether trade-in is selected

true

make

string

Optional

Vehicle make/manufacturer

Volkswagen

model

string

Optional

Vehicle model

Golf

firstRegistrationYear

integer

Optional

Year of first registration

2015

firstRegistrationMonth

string

Optional

Month of first registration

12

mileage

integer

Optional

Vehicle mileage in kilometers

30000

fuelType

string

Optional

Type of fuel. Possible values: PETROL, DIESEL, LPG, CNG, ELECTRICITY, HYBRID, HYDROGENIUM, ETHANOL, HYBRID_DIESEL, OTHER

DIESEL

transmission

string

Optional

Type of transmission. Possible values: MANUAL_GEAR, SEMIAUTOMATIC_GEAR, AUTOMATIC_GEAR

SEMIAUTOMATIC_GEAR

power

integer

Optional

Engine power

150

powerUnit

string

Optional

Unit of power measurement (e.g., kW, HP)

kW

accidentDamaged

boolean

Optional

Whether vehicle has accident damage

false

numberOfPreviousOwners

integer

Optional

Number of previous owners

1

exteriorColor

string

Optional

Exterior color of the vehicle

Black

vehicleIdentificationNumber

string

Optional

Vehicle identification number (VIN)

1M8GDM9AXKP042788

doors

string

Optional

Number of doors. Possible values: TWO_OR_THREE, FOUR_OR_FIVE, SIX_OR_SEVEN

TWO_OR_THREE

category

string

Optional

Vehicle category. Possible values: OtherCar, Cabrio, SmallCar, EstateCar, Limousine, SportsCar, OffRoad, Van

SmallCar

trimLevel

string

Optional

Vehicle trim level

GLC 350e 4MATIC SUV
Delivery
Field Type Required Description Example

selected

boolean

Optional

Whether delivery service is selected

true

city

string

Optional

Delivery city

Berlin

zipCode

string

Optional

Delivery zip code

12345
Financing
Field Type Required Description Example

selected

boolean

Optional

Whether financing is selected

true

downPayment

number

Optional

Down payment amount in euros

10000.0

creditTerm

integer

Optional

Credit term in months

48

monthlyInstallment

number

Optional

Monthly installment amount in euros

200.0

finalInstallment

number

Optional

Final installment amount in euros

null

effectiveInterestRate

number

Optional

Effective interest rate as percentage

null
Leasing
Field Type Required Description Example

selected

boolean

Optional

Whether leasing is selected

true

contractTerm

integer

Optional

Contract term in months

48

downPayment

number

Optional

Down payment amount in euros

10000.0

grossRate

number

Optional

Gross monthly rate in euros

200.0

netRate

number

Optional

Net monthly rate in euros

200.0

mileage

integer

Optional

Annual mileage allowance in kilometers

20000
Vehicle
Example JSON
{
  "vehicle": {
    "mobileAdId": "1241451",
    "make": "BMW",
    "model": "i3",
    "conditionType": "USED",
    "type": "PKW",
    "customerNumber": "154152",
    "internalNumber": "1234",
    "firstRegistration": "2022-11",
    "mileage": 144022,
    "price": "13000"
  }
}
Properties
Field Type Required Description Example

mobileAdId

string

Required

Unique identifier of the ad on the mobile.de platform

1241451

make

string

Required

Vehicle manufacturer

BMW

model

string

Required

Vehicle model

i3

conditionType

string

Required

Condition of the vehicle. Possible values: NEW, USED

USED

type

string

Required

Type of vehicle. Possible values: LKW, KRAD, WOMO, PKW

PKW

customerNumber

string

Required

Customer number associated with the vehicle

123456

internalNumber

string

Optional

Internal vehicle identifier

123456

firstRegistration

string

Optional

Date of first registration - format: YYYY-MM

2022-10

mileage

integer

Optional

Vehicle mileage

179537

price

string

Optional

Vehicle price

48999
Message
Example JSON
{
  "message": {
    "text": "Letzter Preis?"
  }
}
Properties
Field Type Required Description Example

text

string

Required

The text message from the buyer

Letzter Preis?
Source
Example JSON
{
  "source": "MOBILE"
}
Properties
Field Type Required Description Example

source

string

Required

Source platform where the lead originated. Possible values: MOBILE, SANDBOX. SANDBOX is only present in the testing environment.

MOBILE
Make Model Insight

Used within BuyerSearchBehaviourAdded to represent make and model combinations that the buyer has been searching for.

Example JSON
{
  "make": "BMW",
  "model": "3 Series"
}
Properties
Field Type Required Description Example

make

string

Required

The vehicle manufacturer/make

BMW

model

string

Required

The vehicle model

3 Series
Search Insight

Used within BuyerSearchBehaviourAdded to represent insights about fuel types or gear types that the buyer has been searching for.

Example JSON
{
  "value": "DIESEL"
}
Properties
Field Type Required Description Example

value

string

Required

The insight value (e.g., fuel type or gear type)

DIESEL
Search Mileage

Used within BuyerSearchBehaviourAdded to represent the maximum mileage the buyer is searching for.

Example JSON
{
  "max": 50000
}
Properties
Field Type Required Description Example

max

integer

Required

Maximum mileage in kilometers

50000
Search First Registration

Used within BuyerSearchBehaviourAdded to represent the minimum first registration date the buyer is searching for.

Example JSON
{
  "min": "202301"
}
Properties
Field Type Required Description Example

min

string

Required

Minimum first registration in yyyyMM format (e.g., 202301 for January 2023).

202301

Support

Customer Support Contact

Please contact our Customer Support team if you need further assistance. To do so please use our contact form.

FAQ

How to report an error, downtime or a bug?

Please send us a detailed description to service@team.mobile.de containing your method, URL, header, content and error code/message

Where to find the internal number?

The internal number is a reference key used by the seller. Also known as internalNumber or internal-ID. If it is present, then it must be unique per seller. An empty string is treated same as if the element was not present. This field is restricted to a subset of UTF-8 characters. The option can only be switched on/off by the mobile.de customer service. Please contact customer support to request the change.

Difference between mobileSellerId / customerNumber?

All dealer accounts on mobile.de can be identified with their Seller-ID or their Customer Number. For all applicable requests (GET, POST, DELETE) please only use the Seller-ID.

HTTP status and error codes

For a specific list of status and error codes please check our documentation. In case of unlisted status codes please contact customer service via service@team.mobile.de You can also check the current status of the service in Service status.

Suggestions & recommendations on our Lead API and the documentation

Please feel free to send us all of your suggestions to service@team.mobile.de