### Fetch Single Ad Request Example (XML)

Source: https://services.mobile.de/manual/search-api

Example of an HTTP GET request to fetch a single ad using its ad-key. Specifies the resource path, host, and the desired response format as XML.

```http
GET /search-api/ad/456 HTTP/1.0
Host: services.mobile.de
Accept: application/xml
```

--------------------------------

### Retrieve Single Ad - Example Request

Source: https://services.mobile.de/manual/seller-api-legacy

This example demonstrates how to request a single ad using its unique ad-key. The request targets the `/seller-api/sellers/{seller-key}/ads/{ad-key}` resource with a GET method and specifies the expected XML format.

```HTTP
GET /seller-api/sellers/123/ads/456 HTTP/1.0
Host: services.mobile.de
X-MOBILE-SELLER-TOKEN: hf76g364gf6gjdsgfhsdgfzf
Accept: application/vnd.de.mobile.seller-ad-v1.1+xml
```

--------------------------------

### Retrieve All Ads - Example Request

Source: https://services.mobile.de/manual/seller-api-legacy

This example shows the HTTP request to retrieve all ads for a specific seller. It uses a GET method on the `/seller-api/sellers/{seller-key}/ads` resource and specifies the desired XML content type in the Accept header.

```HTTP
GET /seller-api/sellers/123/ads HTTP/1.0
Host: services.mobile.de
X-MOBILE-SELLER-TOKEN: hf76g364gf6gjdsgfhsdgfzf
Accept: application/vnd.de.mobile.seller-ad-v1.1+xml
```

--------------------------------

### GET Request for Sellers

Source: https://services.mobile.de/manual/seller-api-legacy

Example of an HTTP GET request to retrieve seller information from the mobile.de services API. Includes necessary headers like Host and X-MOBILE-SELLER-TOKEN, and specifies the Accept header for the desired XML format.

```HTTP
GET /seller-api/sellers HTTP/1.0
Host: services.mobile.de
X-MOBILE-SELLER-TOKEN: hf76g364gf6gjdsgfhsdgfzf
Accept: application/vnd.de.mobile.seller-v2.0+xml


```

--------------------------------

### Extended Lead XML Example

Source: https://services.mobile.de/manual/changelog

Provides an example of the new, extended XML format for leads, which includes additional service information specified by the consumer.

```XML
<lead>
  <contact>
    <serviceInterest>financing</serviceInterest>
    <serviceInterest>test drive</serviceInterest>
    <financingDetails>
      <desiredAmount>20000</desiredAmount>
      <term>36</term>
    </financingDetails>
  </contact>
</lead>
```

--------------------------------

### Example GET Request for Finding Ads

Source: https://services.mobile.de/manual/search-api

Demonstrates a sample HTTP GET request to the search API, including the resource path and query parameters for filtering ads by exterior color and modification time. It also specifies the accepted content types for the response.

```HTTP
GET /search-api/search?exteriorColor=BLACK&modificationTime.min=2012-05-04T18:13:51.0Z HTTP/1.0
Host: services.mobile.de
Accept: application/xml
```

--------------------------------

### Example API Response (Feature Settings)

Source: https://services.mobile.de/manual/seller-api

An example of a successful HTTP response containing feature settings for a seller, including mobile ad IDs for 'topOfPage' and 'eyeCatcher' booking assistant features.

```JSON
HTTP/1.1 200 OK
Content-Type: application/vnd.de.mobile.api+json

{
  "bookingAssistant": {
    "topOfPage": {
      "mobileAdIds": [
        "405967", "35345003", "5485002"
      ]
    },
    "eyeCatcher": {
      "mobileAdIds": [
        "7891012", "24522453"
      ]
    }
  }
}
```

--------------------------------

### Get Seller API Request and XML Response

Source: https://services.mobile.de/manual/new-seller-api

Illustrates a GET request to the Seller API for a specific seller and presents a sample XML response with seller information and configuration.

```HTTP
GET /seller-api/sellers/12 HTTP/1.1
Accept: application/vnd.de.mobile.api+xml
```

```XML
<?xml version="1.0" encoding="UTF-8"?>
<seller>
  <mobileSellerId>12</mobileSellerId>
  <customerNumber>8</customerNumber>
  <type>DEALER</type>
  <siteId>GERMANY</siteId>
  <readonly>false</readonly>
  <settings>
    <maxImages>15</maxImages>
    <maxHighlights>3</maxHighlights>
    <usedCarSeals>
        <value>VW</value>
        <value>AUDI</value>
    </usedCarSeals>
    <automatedExports>
        <automatedExport>
            <marketplace>ebay-kleinanzeigen.de</marketplace>
            <eligible>true</eligible>
            <active>false</active>
         </automatedExport>
    </automatedExports>
    <videoUrl>true</videoUrl>
  </settings>
  <companyName>Smoke AG</companyName>
</seller>
```

--------------------------------

### Localized Gearboxes Response Example (German)

Source: https://services.mobile.de/manual/seller-api

An example JSON response for the gearboxes endpoint, localized to German, showing the 'name' and 'description' for different gearbox types.

```JSON
{
  "values": [
    {
      "name": "MANUAL_GEAR",
      "description": "Schaltgetriebe"
    },
    {
      "name": "SEMIAUTOMATIC_GEAR",
      "description": "Halbautomatik"
    },
    {
      "name": "AUTOMATIC_GEAR",
      "description": "Automatik"
    }
  ]
}
```

--------------------------------

### GET Request for Single Seller by Key

Source: https://services.mobile.de/manual/seller-api-legacy

Example of an HTTP GET request to retrieve a specific seller's information using their unique key. This request includes the seller key in the resource path and standard headers for authentication and content negotiation.

```HTTP
GET /seller-api/sellers/123 HTTP/1.0
Host: services.mobile.de
X-MOBILE-SELLER-TOKEN: hf76g364gf6gjdsgfhsdgfzf
Accept: application/vnd.de.mobile.seller-v2.0+xml

```

--------------------------------

### Get Seller API Request and JSON Response

Source: https://services.mobile.de/manual/new-seller-api

Demonstrates a GET request to the Seller API for a specific seller and provides a sample JSON response containing seller details and settings.

```HTTP
GET /seller-api/sellers/12 HTTP/1.1
Accept: application/vnd.de.mobile.api+json
```

```JSON
{
    "mobileSellerId": "12",
    "customerNumber": "8",
    "type": "DEALER",
    "siteId": "GERMANY",
    "readonly": false,
    "settings": {
        "maxImages": 30,
        "maxHighlights": 3,
        "usedCarSeals": [
            "VW",
            "AUDI"
        ],
        "automatedExports" : [
            {
                "eligible" : true,
                "marketplace" : "ebay-kleinanzeigen.de",
                "active" : false
            }
        ],
        "videoUrl" : true
    },
    "companyName": "Smoke AG"
}
```

--------------------------------

### Get Seller API Request and XML Response

Source: https://services.mobile.de/manual/seller-api

Illustrates a GET request to the Seller API for a specific seller and presents a sample XML response with seller information and configuration.

```HTTP
GET /seller-api/sellers/12 HTTP/1.1
Accept: application/vnd.de.mobile.api+xml
```

```XML
<?xml version="1.0" encoding="UTF-8"?>
<seller>
  <mobileSellerId>12</mobileSellerId>
  <customerNumber>8</customerNumber>
  <type>DEALER</type>
  <siteId>GERMANY</siteId>
  <readonly>false</readonly>
  <settings>
    <maxImages>15</maxImages>
    <maxHighlights>3</maxHighlights>
    <usedCarSeals>
        <value>VW</value>
        <value>AUDI</value>
    </usedCarSeals>
    <automatedExports>
        <automatedExport>
            <marketplace>ebay-kleinanzeigen.de</marketplace>
            <eligible>true</eligible>
            <active>false</active>
         </automatedExport>
    </automatedExports>
    <videoUrl>true</videoUrl>
  </settings>
  <companyName>Smoke AG</companyName>
</seller>
```

--------------------------------

### Petrol Types Response Example (JSON)

Source: https://services.mobile.de/manual/seller-api

An example JSON response for the petrol types endpoint, showing the structure with 'name' and 'description' for each petrol type.

```JSON
{
  "values": [
    {
      "name": "SUPER_PLUS",
      "description": "Super Plus"
    },
    {
      "name": "SUPER",
      "description": "Super"
    },
    {
      "name": "NORMAL",
      "description": "Normal"
    }
  ]
}
```

--------------------------------

### Get Seller API Request and JSON Response

Source: https://services.mobile.de/manual/seller-api

Demonstrates a GET request to the Seller API for a specific seller and provides a sample JSON response containing seller details and settings.

```HTTP
GET /seller-api/sellers/12 HTTP/1.1
Accept: application/vnd.de.mobile.api+json
```

```JSON
{
    "mobileSellerId": "12",
    "customerNumber": "8",
    "type": "DEALER",
    "siteId": "GERMANY",
    "readonly": false,
    "settings": {
        "maxImages": 30,
        "maxHighlights": 3,
        "usedCarSeals": [
            "VW",
            "AUDI"
        ],
        "automatedExports" : [
            {
                "eligible" : true,
                "marketplace" : "ebay-kleinanzeigen.de",
                "active" : false
            }
        ],
        "videoUrl" : true
    },
    "companyName": "Smoke AG"
}
```

--------------------------------

### Upload Image Reference Example

Source: https://services.mobile.de/manual/new-seller-api

This example shows the expected JSON response when an image is successfully pre-uploaded using the Seller API. The 'ref' field contains a URL that should be included when creating an ad.

```json
{
    "ref": "https://img.classistatic.de/api/v1/mo-prod/images/46/467631f9-acce-1e7f-ca2b-9f13912d713b?rule=mo-640.jpg"
}
```

--------------------------------

### Error Response - New XML Example

Source: https://services.mobile.de/manual/search-api

Shows an example of an error response in the new XML format for an invalid search parameter, detailing the error key, message, and arguments associated with the error.

```XML
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<errorResponse>
    <errors>
        <error>
            <key>invalid-search-parameter</key>
            <message>Invalid search parameter</message>
            <args>
                <arg>
                    <key>field</key>
                    <value>exteriorColor</value>
                </arg>
                <arg>
                    <key>code</key>
                    <value>typeMismatch</value>
                </arg>
                <arg>
                    <key>rejected-value</key>
                    <value>Black1</value>
                </arg>
            </args>
        </error>
    </errors>
</errorResponse>
```

--------------------------------

### Upload Image Reference Example

Source: https://services.mobile.de/manual/seller-api

This example shows the expected JSON response when an image is successfully pre-uploaded using the Seller API. The 'ref' field contains a URL that should be included when creating an ad.

```json
{
    "ref": "https://img.classistatic.de/api/v1/mo-prod/images/46/467631f9-acce-1e7f-ca2b-9f13912d713b?rule=mo-640.jpg"
}
```

--------------------------------

### Filter by Operating Weight

Source: https://services.mobile.de/manual/search-api

This example shows how to filter vehicles by their operating weight, using the 'operatingWeight.min' and 'operatingWeight.max' parameters. The example sets a minimum of 1 and a maximum of 20.

```URL
https://services.mobile.de/search-api/search?operatingWeight.min=1&operatingWeight.max=20
```

--------------------------------

### Get Hydraulic Installation Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving hydraulic installation reference data.

```HTTP
GET /refdata/hydraulicinstallations
```

--------------------------------

### Get Exterior Auto Panorama (Curl)

Source: https://services.mobile.de/manual/new-seller-api

Example using cURL to retrieve an exterior Auto Panorama. It sends a GET request to the specified endpoint with the appropriate Accept header.

```Curl
curl -X GET 'https://services.mobile.de/seller-api/sellers/28481/ads/34561/auto-panorama/exterior' \
     -H 'Accept: application/vnd.de.mobile.api+json'
```

--------------------------------

### XML Parsing Error Response Example

Source: https://services.mobile.de/manual/new-seller-api

Provides an example of an XML error response from the Seller API, detailing a parsing error with specific messages and location information.

```XML
<?xml version="1.0" encoding="UTF-8"?>
<errorResponse>
  <errors>
    <error>
      <key>xml-parse-error</key>
      <args>
        <arg>
          <key>parser-message</key>
          <value>ParseError at [row,col]:[1,768]
Message: The element type "vehicleClass" must be terminated by the matching end-tag "</value>
        </arg>
        <arg>
          <key>line</key>
          <value>1</value>
        </arg>
        <arg>
          <key>column</key>
          <value>768</value>
        </arg>
      </args>
    </error>
  </errors>
</errorResponse>
```

--------------------------------

### API Resource: Get All Image URLs (GET)

Source: https://services.mobile.de/manual/seller-api-legacy

This entry details the API call to retrieve all image URLs for a specific advertisement. It includes the resource path, the GET method, and the required headers.

```http
GET /seller-api/sellers/{seller-key}/ads/{adId}/images
Content-Type: application/vnd.de.mobile.seller-ad-v1.1+xml
Accept: application/vnd.de.mobile.seller-ad-v1.1+xml
```

--------------------------------

### XML Parsing Error Response Example

Source: https://services.mobile.de/manual/seller-api

Provides an example of an XML error response from the Seller API, detailing a parsing error with specific messages and location information.

```XML
<?xml version="1.0" encoding="UTF-8"?>
<errorResponse>
  <errors>
    <error>
      <key>xml-parse-error</key>
      <args>
        <arg>
          <key>parser-message</key>
          <value>ParseError at [row,col]:[1,768]
Message: The element type "vehicleClass" must be terminated by the matching end-tag "</value>
        </arg>
        <arg>
          <key>line</key>
          <value>1</value>
        </arg>
        <arg>
          <key>column</key>
          <value>768</value>
        </arg>
      </args>
    </error>
  </errors>
</errorResponse>
```

--------------------------------

### Get Exterior Auto Panorama (Curl)

Source: https://services.mobile.de/manual/seller-api

Example using cURL to retrieve an exterior Auto Panorama. It sends a GET request to the specified endpoint with the appropriate Accept header.

```Curl
curl -X GET 'https://services.mobile.de/seller-api/sellers/28481/ads/34561/auto-panorama/exterior' \
     -H 'Accept: application/vnd.de.mobile.api+json'
```

--------------------------------

### Accessing Swagger Sandbox Documentation

Source: https://services.mobile.de/manual/new-seller-api

Instructions for accessing the Swagger UI for the mobile.de Seller-API sandbox environment. This allows developers to test API functionalities in a staging environment before deploying to production.

```text
Open https://services.sandbox.mobile.de/seller-api/openapi-docs
In the 'Servers' section, choose https://services.sandbox.mobile.de/seller-api
Click on 'Authorize' button and enter your credentials
Test all the APIs
```

--------------------------------

### Upload Images - PUT Request Example

Source: https://services.mobile.de/manual/seller-api-legacy

Illustrates a PUT request for uploading images to an ad. This example shows the resource path, HTTP method, and the multipart/form-data content type with a boundary.

```HTTP
PUT /seller-api/sellers/123/ads/456/images HTTP/1.0
Host: services.mobile.de
X-MOBILE-SELLER-TOKEN: hf76g364gf6gjdsgfhsdgfzf
Content-Type: multipart/form-data; boundary=vjrLeiXjJaWiU0JzZkUPO1rMcE2HQ-n7XsSx
Accept: application/vnd.de.mobile.seller-ad-v1.1+xml
```

--------------------------------

### Book Features Using New Resource

Source: https://services.mobile.de/manual/changelog

This code example illustrates how to book features using the new resource, specifically showing the JSON structure for activating 'topOfPage' and 'eyeCatcher' features.

```JSON
"bookableFeatures":{
"topOfPage":{"active":true},
"eyeCatcher":{"active":false}
}
```

--------------------------------

### Get Gearbox Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving gearbox reference data.

```HTTP
GET /refdata/gearboxes
```

--------------------------------

### Image URL Migration Example

Source: https://services.mobile.de/manual/changelog

Provides examples of old eBay image URLs and their corresponding new mobile.de image URLs. This is crucial for data providers to update their stored references to avoid image loss on the site.

```text
Old eBay picture reference: https://i.ebayimg.com/00/s/ODBYODA=/z/d4MAAOSw~o5acwdL/$_27.JPG
New picture picture reference: https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-640.jpg
```

--------------------------------

### Error Response - Legacy XML Example

Source: https://services.mobile.de/manual/search-api

Provides an example of an error response in legacy XML format for an invalid search parameter, detailing the error key, message, and specific arguments related to the error.

```XML
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  <error:errors xmlns:error="http://services.mobile.de/schema/common/error-1.0">
    <error:error key="invalid-search-parameter" message="Invalid search parameter">
      <error:args key="field">exteriorColor</error:args>
      <error:args key="code">typeMismatch</error:args>
      <error:args key="rejected-value">BLACK11,RED</error:args>
    </error:error>
</error:errors>
```

--------------------------------

### Get Color Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving color reference data.

```HTTP
GET /refdata/colors
```

--------------------------------

### Search API Response Example (New XML)

Source: https://services.mobile.de/manual/changelog

Illustrates an example of a search API response using the new XML format, incorporating the updated consumption and emission data fields required by PKW EnVKV 2024.

```XML
GET /search-api/search/ HTTP/1.1
Host: services.mobile.de
Content-Type: application/vnd.de.mobile.api+xml
...
<ad>
...
<emissions>
<combined>
<co2>23</co2>
<co2Class>B</co2Class>
</combined>
<discharged>
<co2Class>D</co2Class>
</discharged>
</emissions>
<consumptions>
<weightedCombinedFuel>4.8</weightedCombinedFuel>
<weightedCombinedPower>10.2</weightedCombinedPower>
<fuel>
<combined>4.4</combined>
</fuel>
<power>
<combined>14.4</combined>
</power>
</consumptions>
...
</ad>
...
```

--------------------------------

### Get Battery Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving battery reference data.

```HTTP
GET /refdata/batteries
```

--------------------------------

### Example of Path Parameters in URL

Source: https://services.mobile.de/manual/new-seller-api

Demonstrates how path parameters are used in a URL to identify specific resources, showing a URL with placeholder parameters and its resolved form.

```URL
/seller-api/sellers/:mobileSellerId/ads/:mobileAdId
/seller-api/sellers/12/ads/34
```

--------------------------------

### Get Airbag Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving airbag reference data.

```HTTP
GET /refdata/airbags
```

--------------------------------

### Accessing Swagger Sandbox Documentation

Source: https://services.mobile.de/manual/seller-api

Instructions for accessing the Swagger UI for the mobile.de Seller-API sandbox environment. This allows developers to test API functionalities in a staging environment before deploying to production.

```text
Open https://services.sandbox.mobile.de/seller-api/openapi-docs
In the 'Servers' section, choose https://services.sandbox.mobile.de/seller-api
Click on 'Authorize' button and enter your credentials
Test all the APIs
```

--------------------------------

### Example API Response (Seller Data)

Source: https://services.mobile.de/manual/seller-api

An example of a successful HTTP response containing seller data, including ID, customer number, site ID, and various settings like image limits and marketplace configurations.

```JSON
HTTP/1.1 200 OK
Content-Type: application/vnd.de.mobile.api+json

{
    "mobileSellerId": "12",
    "customerNumber": "8",
    "type": "DEALER",
    "siteId": "GERMANY",
    "readonly": false,
    "settings": {
        "maxImages": 30,
        "maxHighlights": 3,
        "usedCarSeals": [
            "VW",
            "AUDI"
        ],
        "automatedExports" : [
            {
                "eligible" : true,
                "marketplace" : "ebay-kleinanzeigen.de",
                "active" : false
            }
        ],
        "videoUrl" : true,
        "leasing": {
            "maxPrivateRates": 16,
            "maxCommercialRates": 16
        },
        "directOffer": {
            "eligible": true,
            "blocked": false
        }
    },
    "companyName": "Smoke AG",
    "billingForecast": {
        "billingPeriod": "2017-07",
        "calculationDate": "2017-07-23",
        "invoiceLanguage": "de",
        "currency": "EUR",
        "invoiceItems": [
            {
                "descriptor": "VEHICLE_COUNT",
                "accountType": "GOLD",
                "fromDate": "2017-07-01",
                "toDate": "2017-07-31",
                "unitPrice": "169.99",
                "totalPrice": "169.99",
                "articleCount": "8.04",
                "quantityAmount": "23.0",
                "quantityUnit": "DAY"
            },
            {
                "descriptor": "VEHICLE_INSERTION",
                "accountType": "",
                "fromDate": "2017-07-01",
                "toDate": "2017-07-31",
                "unitPrice": "2.99",
                "totalPrice": "0.0",
                "articleCount": "8.0",
                "quantityAmount": "0.0",
                "quantityUnit": "ITEM"
            }
        ],
        "freeContingents": [
            {
                "descriptor": "TOP_OF_PAGE",
                "description": "Top-Inserat inkl. kostenfreiem Kontingent",
                "available": "0",
                "contingentUnlimited": false
            }
        ]
    }
}
```

--------------------------------

### Delete Ad - DELETE Request Example

Source: https://services.mobile.de/manual/seller-api-legacy

Provides an example of a DELETE request to remove an ad. It includes the resource path, HTTP method, host, and authentication token.

```HTTP
DELETE /seller-api/sellers/123/ads/456 HTTP/1.0 Host: services.mobile.de X-MOBILE-SELLER-TOKEN: hf76g364gf6gjdsgfhsdgfzf
```

--------------------------------

### Accessing Swagger Documentation

Source: https://services.mobile.de/manual/new-seller-api

Instructions on how to access and use the Swagger UI for the mobile.de Seller-API to test API endpoints. This involves navigating to the documentation URL, selecting the server, authorizing with credentials, and testing the APIs.

```text
Open https://services.mobile.de/seller-api/openapi-docs
In the 'Servers' section, choose https://services.mobile.de/seller-api
Click on 'Authorize' button and enter your credentials
Test all the APIs
```

--------------------------------

### Get Site-Specific Classes

Source: https://services.mobile.de/manual/search-api

This example shows how to retrieve class data that is specific to a given Site ID.

```HTTP
GET /refdata/sites/:siteId/classes
```

--------------------------------

### Example of Path Parameters in URL

Source: https://services.mobile.de/manual/seller-api

Demonstrates how path parameters are used in a URL to identify specific resources, showing a URL with placeholder parameters and its resolved form.

```URL
/seller-api/sellers/:mobileSellerId/ads/:mobileAdId
/seller-api/sellers/12/ads/34
```

--------------------------------

### Search API Response Example (Legacy XML)

Source: https://services.mobile.de/manual/changelog

Provides an example of a search API response in Legacy XML format, showcasing the new data fields for CO2 emissions and consumption values as per PKW EnVKV 2024.

```XML
GET /search-api/search/ HTTP/1.1
Host: services.mobile.de
Content-Type: application/xml
...
<ad:specifics>
...
<ad:emissions>
<ad:combined co2="23" co2-class="B"/>
<ad:discharged co2-class="D"/>
</ad:emissions>
<ad:consumptions>
<ad:weighted-combined-fuel value="4.8">
<ad:weighted-combined-power value="10.2">
<ad:fuel-consumption combined="4.4"/>
<ad:power-consumption combined="14.4"/>
</ad:weighted-combined-power>
</ad:weighted-combined-fuel>
...
<ad:specifics>
...
```

--------------------------------

### Example Response for Seller Data

Source: https://services.mobile.de/manual/new-seller-api

An example of a successful HTTP response containing seller data, including ID, customer number, type, site ID, and various settings related to image uploads, highlights, used car seals, automated exports, video URLs, and leasing options.

```HTTP
HTTP/1.1 200 OK
Content-Type: application/vnd.de.mobile.api+json

{
    "mobileSellerId": "12",
    "customerNumber": "8",
    "type": "DEALER",
    "siteId": "GERMANY",
    "readonly": false,
    "settings": {
        "maxImages": 30,
        "maxHighlights": 3,
        "usedCarSeals": [
            "VW",
            "AUDI"
        ],
        "automatedExports" : [
            {
                "eligible" : true,
                "marketplace" : "ebay-kleinanzeigen.de",
                "active" : false
            }
        ],
        "videoUrl" : true,
        "leasing": {
            "maxPrivateRates": 16,
            "maxCommercialRates": 16
        },
        "directOffer": {
            "eligible": true,
            "blocked": false
        }
    },
    "companyName": "Smoke AG",
    "billingForecast": {
        "billingPeriod": "2017-07",
        "calculationDate": "2017-07-23",
        "invoiceLanguage": "de",
        "currency": "EUR",
        "invoiceItems": [
            {
                "descriptor": "VEHICLE_COUNT",
                "accountType": "GOLD",
                "fromDate": "2017-07-01",
                "toDate": "2017-07-31",
                "unitPrice": "169.99",
                "totalPrice": "169.99",
                "articleCount": "8.04",
                "quantityAmount": "23.0",
                "quantityUnit": "DAY"
            },
            {
                "descriptor": "VEHICLE_INSERTION",
                "accountType": "",
                "fromDate": "2017-07-01",
                "toDate": "2017-07-31",
                "unitPrice": "2.99",
                "totalPrice": "0.0",
                "articleCount": "8.0",
                "quantityAmount": "0.0",
                "quantityUnit": "ITEM"
            }
        ],
        "freeContingents": [
            {
                "descriptor": "TOP_OF_PAGE",
                "description": "Top-Inserat inkl. kostenfreiem Kontingent",
                "available": "0",
                "contingentUnlimited": false
            }
        ]
    }
}
```

--------------------------------

### Get Wheel Formula Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving wheel formula reference data.

```HTTP
GET /refdata/wheelformulas
```

--------------------------------

### Get Usage Type Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving usage type reference data.

```HTTP
GET /refdata/usagetypes
```

--------------------------------

### Accessing Swagger Documentation

Source: https://services.mobile.de/manual/seller-api

Instructions on how to access and use the Swagger UI for the mobile.de Seller-API to test API endpoints. This involves navigating to the documentation URL, selecting the server, authorizing with credentials, and testing the APIs.

```text
Open https://services.mobile.de/seller-api/openapi-docs
In the 'Servers' section, choose https://services.mobile.de/seller-api
Click on 'Authorize' button and enter your credentials
Test all the APIs
```

--------------------------------

### Get Speed Control Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving speed control reference data.

```HTTP
GET /refdata/speedcontrols
```

--------------------------------

### Example of a Newly Created Ad Location Header

Source: https://services.mobile.de/manual/seller-api-legacy

This example shows the 'Location' HTTP header returned after a successful creation of an ad. It includes the URL of the newly created resource, highlighting the ad-key.

```http
Location: https://services.mobile.de/seller-api/sellers/123/ads/456
```

--------------------------------

### Get Radio Type Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving radio type reference data.

```HTTP
GET /refdata/radiotypes
```

--------------------------------

### Get Price Rating Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving price rating reference data.

```HTTP
GET /refdata/pricerating
```

--------------------------------

### Get Petrol Type Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving petrol type reference data.

```HTTP
GET /refdata/petroltypes
```

--------------------------------

### API Resource: Create Ad (POST)

Source: https://services.mobile.de/manual/seller-api-legacy

This entry outlines the process for creating a new advertisement via the API. It specifies the resource path, the POST method, and the required headers for submitting ad data.

```http
POST /seller-api/sellers/{seller-key}/ads
Content-Type: application/vnd.de.mobile.seller-ad-v1.1+xml
Accept: application/vnd.de.mobile.seller-ad-v1.1+xml
```

--------------------------------

### Get Parking Assistant Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving parking assistant reference data.

```HTTP
GET /refdata/parkingassistants
```

--------------------------------

### DirectOfferSettings Configuration

Source: https://services.mobile.de/manual/new-seller-api

Defines settings for direct offers, indicating account eligibility and whether the account is blocked from creating direct offers by customer support.

```json
{
  "eligible": "Boolean",
  "blocked": "Boolean"
}
```

--------------------------------

### Get Motor Position Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving motor position reference data.

```HTTP
GET /refdata/motorpositions
```

--------------------------------

### Get Interior Type Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving interior type reference data.

```HTTP
GET /refdata/interiortypes
```

--------------------------------

### Get Heating Type Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving heating type reference data.

```HTTP
GET /refdata/heatingtypes
```

--------------------------------

### Get Frame Material Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving frame material reference data.

```HTTP
GET /refdata/framematerials
```

--------------------------------

### Get Emission Class Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving emission class reference data.

```HTTP
GET /refdata/emissionclasses
```

--------------------------------

### Get Driving Modes Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving driving modes reference data.

```HTTP
GET /refdata/drivingmodes
```

--------------------------------

### Get Door Count Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving door count reference data.

```HTTP
GET /refdata/doorcounts
```

--------------------------------

### Example Search for Multiple Colors and Date

Source: https://services.mobile.de/manual/search-api

Demonstrates a search query to find vehicles with specific exterior colors (BLACK and RED) and a minimum first registration date.

```URL
https://services.mobile.de/search-api/search?exteriorColor=BLACK&exteriorColor=RED&firstRegistrationDate.min=2008-05
```

--------------------------------

### Get Country Version Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving country version reference data.

```HTTP
GET /refdata/countryversion
```

--------------------------------

### Preview Ad Price Rating Response (HTTP)

Source: https://services.mobile.de/manual/new-seller-api

An example of a successful HTTP response for previewing an ad's price rating, including price ranges and labels.

```http
HTTP/1.1 200 OK
Content-Length: 314
Content-Type: application/vnd.de.mobile.api+json

{
  "label": "INCREASED_PRICE",
  "labelRanges": [
    {
      "label": "VERY_GOOD_PRICE",
      "from": "13600",
      "to": "16200"
    },
    {
      "label": "GOOD_PRICE",
      "from": "16200",
      "to": "17300"
    },
    {
      "label": "REASONABLE_PRICE",
      "from": "17300",
      "to": "19200"
    },
    {
      "label": "INCREASED_PRICE",
      "from": "19200",
      "to": "21400"
    },
    {
      "label": "HIGH_PRICE",
      "from": "21400",
      "to": "23100"
    }
  ]
}
```

--------------------------------

### Get Breakdown Service Reference Data

Source: https://services.mobile.de/manual/search-api

This example shows the endpoint for retrieving breakdown service reference data.

```HTTP
GET /refdata/breakdownservices
```

--------------------------------

### Get Makes by Class

Source: https://services.mobile.de/manual/search-api

This example shows how to retrieve make data, which can be filtered by class and optionally by site ID.

```HTTP
GET /refdata/classes/:class/makes
GET /refdata/sites/:siteId/classes/:class/makes
```

--------------------------------

### POST Request to Create Ad

Source: https://services.mobile.de/manual/seller-api-legacy

Example of an HTTP POST request to create a new ad for a seller. This includes the seller key in the URL, authentication token, and specifies the content type for the ad data in XML format.

```HTTP
POST /seller-api/sellers/123/ads HTTP/1.0 Host: services.mobile.de X-MOBILE-SELLER-TOKEN: hf76g364gf6gjdsgfhsdgfzf Content-Type: application/vnd.de.mobile.seller-ad-v1.1+xml

```

--------------------------------

### Get Petrol Types Response (JSON)

Source: https://services.mobile.de/manual/new-seller-api

Example JSON response containing a list of petrol types with their names and descriptions.

```JSON
{
  "values": [
    {
      "name": "SUPER_PLUS",
      "description": "Super Plus"
    },
    {
      "name": "SUPER",
      "description": "Super"
    },
    {
      "name": "NORMAL",
      "description": "Normal"
    }
  ]
}
```

--------------------------------

### Get Categories by Class

Source: https://services.mobile.de/manual/search-api

This snippet demonstrates fetching categories associated with a specific class, with examples for both site-independent and site-specific retrieval.

```HTTP
GET /refdata/classes/:class/categories
GET /refdata/sites/:siteId/classes/:class/categories
```

--------------------------------

### Example of Created Ad Location Header

Source: https://services.mobile.de/manual/new-seller-api

Illustrates the 'Location' HTTP header returned after a successful POST request to create an ad, containing the URL of the newly created resource.

```HTTP
Location: https://services.mobile.de/seller-api/sellers/123/ads/456
```

--------------------------------

### Mobile Ad JSON Example

Source: https://services.mobile.de/manual/new-seller-api

This snippet displays a sample JSON object for a mobile advertisement. It includes various fields such as mobileAdId, vehicle details (make, model, category), condition, registration information, mileage, technical specifications (cubicCapacity, power, gearbox, fuel), emission details, consumption data, cost model information, exterior and interior features, safety attributes (abs, esp), a textual description, and pricing details (dealer and consumer prices, VAT, currency).

```JSON
{
  "mobileAdId": "123456789",
  "mobileSellerId": "98761",
  "creationDate": "2016-12-06T12:55:36+01:00",
  "modificationDate": "2017-03-02T14:22:47+01:00",
  "uploadSticky": false,
  "vehicleClass": "Car",
  "category": "EstateCar",
  "make": "AUDI",
  "model": "A4",
  "modelDescription": "A4 Avant 2.0 TFSI multitronic Attraction",
  "condition": "USED",
  "firstRegistration": "201002",
  "mileage": 800,
  "cubicCapacity": 1984,
  "power": 155,
  "gearbox": "AUTOMATIC_GEAR",
  "fuel": "PETROL",
  "emissionSticker": "EMISSIONSSTICKER_GREEN",
  "images": [
        {
          "ref": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-acce-1e7f-ca2b-9f13912d713b?rule=mo-640.jpg",
          "hash": "fda8487ed7fcfbecdf1eb55cf582fccf"
        },
        {
          "ref": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-acce-1d7f-ca2b-9f13912d713b?rule=mo-640.jpg",
          "hash": "fda8487ed7fcfbecdf1eb55cf582fccf"
        }
  ],
  "emissionClass": "EURO4",
  "emissions": {
        "combined": {
            "co2": 86.0,
            "co2Class": "C"
        }
    },
  "consumptions": {
        "fuel": {
            "city": 5.4,
            "suburban": 4.0,
            "rural": 4.2,
            "highway": 6.4,
            "combined": 4.4
        }
    },
  "costModel": {
        "fuelPrice": "1.75",
        "consumptionPriceYear": 2024,
        "co2Costs": {
            "low": {
                "basePrice": "45",
                "accumulated": "2345"
            },
            "middle": {
                "basePrice": "55",
                "accumulated": "3345"
            },
            "high": {
                "basePrice": "65",
                "accumulated": "4345"
            }
        },
        "tax": "234.4",
        "timeFrame": {
            "from": 2024,
            "till": 2034
        },
        "consumptionCosts": "3234"
  },
  "exteriorColor": "SILVER",
  "manufacturerColorName": "Silver Moon",
  "doors": "FOUR_OR_FIVE",
  "seats": 5,
  "interiorColor": "GREY",
  "interiorType": "ALCANTARA",
  "generalInspection": "201402",
  "constructionDate": "2010-07-15T00:00:00+02:00",
  "numberOfPreviousOwners": 2,
  "countryVersion": "DE",
  "damageUnrepaired": false,
  "roadworthy": false,
  "abs": true,
  "airbag": "FRONT_AND_SIDE_AND_MORE_AIRBAGS",
  "alloyWheels": true,
  "centralLocking": true,
  "climatisation": "AUTOMATIC_CLIMATISATION",
  "electricHeatedSeats": true,
  "electricWindows": true,
  "esp": true,
  "immobilizer": true,
  "powerAssistedSteering": true,
  "description": "This is really a nice car. The only strange thing is that so called flux capacitor that it is equipped with. The previous owner told me that he took it from an old DeLorean. No idea what it is good for.",
  "schwackeCode": 10110413,
  "deliveryPeriod": 6,
  "price": {
        "dealerPriceGross": "13090.00",
        "consumerPriceGross": "13090.00",
        "dealerPriceNet": "11000.00",
        "consumerPriceNet": "11000.00",
        "vatRate": "19.00",
        "type": "FIXED",
        "currency": "EUR"
  }
}
```