Changelog

24.10.2024 Removal of deprecated field in Seller API

The following field is deprecated and will be ignored by Seller-API starting from KW 48 (25.11-01.12.).

Affected Interfaces: Seller-API

23.09.2024 Extension of individual contact feature

We are currently working on improving the individual contact feature available from Silver package onwards. The SellerAPI will be extended to allow the creation, update and deletion of individual contacts in addition to the existing GET endpoint. Additionally, we will introduce the feature of automatically assigning individual contacts to listings. This matching process will be based on a new, optional attribute (responsibilities) added to the schema of an individual contact:

        
            {
                "firstName": "Mr",
                ...
                "responsibilities": [
                  {
                    "vehicleClass": "Car",
                    "condition": "USED",
                    "usageType": "DEMONSTRATION",
                    "make": "BMW"
                  }
                ]
              }
        
    

Responsibilities are a list of already known attributes and describe what kind of vehicles fall under the responsibility of a certain contact person.

Example: contact person X is responsible for all BMW used cars at dealership Y. Dealership Y creates a new contact person via the API using the following payload:

        
            POST /seller-api/sellers/12/individual-contacts HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/vnd.de.mobile.api+json
            {
                "firstName": "Mr",
                "lastName": "BMW",
                "email": "mr.bmw@bmw.de",
                "phone": {
                  "number": "4556",
                  "areaCode": "123",
                  "countryCallingCode": "49"
                },
                "jobTitle": "BMW Sales Manager",
                "responsibilities": [
                  {
                    "vehicleClass": "Car",
                    "condition": "USED",
                    "make": "BMW"
                  }
                ]
              }
        
    

The automatic assignment runs on every update to the field responsibilities. It processes the dealer's inventory and assigns all matching listings to the contact person. Dealership Y ends up having all used car BMWs that are not already assigned to a contact person assigned to Mr BMW.

For the sake of completeness, the following two requests display the update and deletion of an individual contact:

        
            PUT /seller-api/sellers/12/individual-contacts/64c232e9c19479425a9bb5c4 HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/vnd.de.mobile.api+json
            {
                "firstName": "Mr",
                ...
                "jobTitle": "BMW Sales Manager",
                "responsibilities": [
                  {
                    "vehicleClass": "Ebike",
                    "condition": "NEW",
                    "make": "BUTCHERS AND BICYCLES"
                  }
                ]
              }
        
    

        
            DELETE /seller-api/sellers/12/individual-contacts/64c232e9c19479425a9bb5c4 HTTP/1.1
            Host: services.mobile.de
        
    

Within this change, we will also roll out the "useDefaultContact" flag on a listing level:

This flag is needed to opt-out of the automatic assignment of individual contacts to a listing. Even if no individual contact data is sent in the request an automatically assigned contact will not be removed. If the flag is set to true, the dealer will be kept as the listing's contact person. It has to be sent in the same way as the individualContactId, e.g. via ad creation request:

        
            POST /seller-api/sellers/12/ads HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/vnd.de.mobile.api+json

            {
                "vehicleClass": "EBike",
                "make": "BUTCHERS AND BICYCLES",
                "modelDescription": "Some Description",
                "condition": "NEW",
                "category": "CityBike",
                "damageUnrepaired": false,
                ...
                "manufacturerColorName": "schwarz",
                "price": {
                    "consumerPriceGross": "20498.94",
                    "vatRate": "19.00",
                    "type": "FIXED",
                    "currency": "EUR"
                },
                "description": "This is really a nice e-bike.",
                "useDefaultContact": true, <- new
                "nationalDelivery": {
                    "radius": 400,
                    "period": 90,
                    "fee": 50,
                    "additionalInformation": "Delivery via our service provider."
                }
            }
        
    

The default behavior however stays as is: if there is no individualContactId provided and also no matching contact found the dealer is considered the contact person.

If both an individualContactId and useDefaultContact are sent the individualContactId will be ignored and a warning returned:

    
        {
          "warnings": [
            {
              "key": "conflicting-field",
              "args": [
                {
                  "key": "path",
                  "value": "individualContactId"
                },
                {
                  "key": "cause",
                  "value": "IndividualContactId is ignored when useDefaultContact is present."
                }
              ]
            }
          ]
        }
    
    

The mentioned changes will be released in KW 42/2024. From there on there is no need to enter the dealer area anymore to use the individual contact feature.

Affected Interfaces: Seller-API

01.08.2024 Warnings in SellerAPI related to missing EnVKV data

Soon the SellerAPI will provide warnings when relevant EnVKV data is missing. This should give more guidance and ensure that all the data is provided when we might make these fields mandatory in the future.

Within this change, we will also roll out the "incomplete" flag to skip EnVKV validation, for example, for oldtimers with low mileage. This decision is up to the users.

The warning is just additional information and is currently not having any impact on the listing creation/update.

Example warning:

    
        {
          "warnings": [
            {
              "key": "FUTURE_VALIDATION_ERROR",
              "args": [
                {
                  "key": "path",
                  "value": "emissions.combined.co2"
                }
              ]
            },
            {
              "key": "FUTURE_VALIDATION_ERROR",
              "args": [
                {
                  "key": "path",
                  "value": "emissions.combined.co2Class"
                }
              ]
            }
          ]
        }
    
    

Affected Interfaces: Seller-API

24.07.2024 New vehicle attributes are live!

All changes related to the new attributes communicated on June 13, 2024, for the Seller API and on June 14, 2024, for the Search API are now live. The Seller API now supports creating listings with these new and updated attributes, while the Search API offers the new attributes and supports the newly added filters.

Please refer to this page for a comprehensive overview of the changes for Seller API and here for Search API.

Affected Interfaces: Seller-API Search-API

14.06.2024 Search API New vehicle attributes

We are excited to announce that our Search API will be updated around mid to late July with new attributes and filters! These attributes will be available through the ad detail endpoint, and users will be able to search for ads based on these new attributes using the newly introduced filters.

For a detailed overview of the new attributes and the filters with examples, please refer here.

Affected Interfaces: Search-API

13.06.2024 New vehicle attributes

We are delighted to announce that around mid to late July, we will be introducing new attributes to various vehicle categories. Additionally, some existing attributes will be extended with new values, and certain attributes from other categories will be made available across different categories.

These enhancements will allow our dealers to include more precise and comprehensive details about each vehicle, resulting in improved listing quality and better search options.

Please refer to this page for a comprehensive overview of the upcoming changes.

Affected Interfaces: Seller-API

19.05.2024 Enhanced Search API Now Supports Two New Data Formats!

We're excited to announce the immediate availability of two additional data formats within our Search API, along with comprehensive updates to our documentation. These enhancements aim to enhance user experience and provide clear instructions for utilizing our API.

1. New Data Formats: We're introducing two new modern data formats for seamless integration with the Search API.
2. Updated Documentation: Our Search API documentation has been updated, featuring:
   • A redesigned interface for enhanced user-friendliness.
   • Structured insights into utilizing the API effectively.
   • Detailed guidance on the newly introduced data formats.

Action Recommended: We encourage transitioning from the legacy XML format to take advantage of the benefits offered by the new data formats. Please be aware that while the legacy format remains available, it is now deprecated.

Rest assured, these updates will not disrupt the current behavior of API users.

For comprehensive details on the new data formats, refer to the dedicated Data Format section in our documentation.

Access the updated Search API documentation here.

Affected Interfaces: Search-API

30.04.2024 SellerAPI changes related to the new EnVKV

We are planning to introduce some more functionality in the SellerAPI related to the new EnVKV changes and adjusted the timing of introducing mandatory fields:

• Mandatory fields (as communicated on 26.03.) will go live on 06.05.2024 (instead of 29.04.)
• We removed the validation for old EnVKV/WLTP fields. Those data fields are not needed anymore and should not be sent. However, if the envkvCompliant is sent as true, the validation for the old fields will be activated again for this specific API call. The envkvCompliant is not relevant for the new consumption fields and should not be used anymore.
• The validation of the costModel section will be more strict (this will happen on 20.05.2024):
  • the following fields have to be sent completely filled or left out/sent with NULL altogether:

          
              /costModel/co2Costs/middle/{basePrice/accumulated}
              /costModel/co2Costs/low/{basePrice/accumulated}
              /costModel/co2Costs/high/{basePrice/accumulated}
              /costModel/timeFrame/from
              /costModel/timeFrame/till
          
          

• We will introduce a new flag to indicate that a required EnVKV value is missing by intend:

        
                "envkv": {
                    "incomplete" : true
               }
        
        

Example:

        
            ...
                "model": "A4",
                "modelDescription": "Neuer A4",
                "condition": "NEW",
                "fuel": "PETROL",
                "cubicCapacity": 1545,
                "envkv": {
                    "incomplete" : true
                },
                "emissions": {
                    "combined": {
                        "co2": "86",
                        "co2Class": "C"
                    }
                },
                "consumptions": {
                    "fuel": {
                        "combined": "4.4",
                        "city": "5.4",
                        "suburban": "4.0",
                        "rural": "4.2",
                        "highway": "6.4"
                    }
                },
            ...
        
        

This is meant for cases where some values are not provided by the OEM or for example it is a rather old vehicle (before WLTP time) with a very low mileage.

Still, in this case the EnVKV is relevant for this specific listing and it's the dealers' responsibility to provide all the required information where possible.

Affected Interfaces: Seller-API

17.04.2024 Protecting automatic leasing rates / new error code in Seller-API for leasing

In CW20 We will introduce a new error code in the leasing part of the Seller-API. In case there have been automatic leasing rates calculated for a listing via the dealer area, it will no longer be possible to update or delete these rates through the API. In this case, we return the error automatic_leasing_overwrite_protection

Automatic leasing itself is not available through the API (yet). Please remove the rates manually via the dealer area to be again able to update or delete them via the API.

Affected Interfaces: Seller-API

08.04.2024 New data fields for PKW EnVKV 2024

From around CW18 - 29th of April it will be possible to see the newly required consumption and emission values according to the new PKW-EnVKV released in Feb 2024.

The following table describes which fields will be provided with search response:

Example Search Response with new values (Legacy 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:consumptions>
                ...
            <ad:specifics>
            ...
        
    

Example Search Response with new values (New 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>
            ...
        
    

The following table describes which fields will be provided with Ad Detail Response and with AdStream:

Example Ad Detail Response with new values (Legacy XML)

        
            GET /search-api/ad/123 HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/xml
            ...
            <ad:specifics>
                ...
                <ad:equivalent-all-electric-range value="48"/>
                <ad:emissions>
                   <ad:combined co2="23" co2-class="B" />
                   <ad:discharged co2="123" co2-class="D" />
                </ad:emissions>
                <ad:consumptions>
                    <ad:weighted-combined-fuel value="4.4">
                    <ad:weighted-combined-power value="10.8">
                   <ad:fuel-consumption combined="4.4" city="5.4" suburban="4.0" rural="4.2" highway="6.4"/>
                   <ad:power-consumption combined="14.4" city="12.4" suburban="13.4" rural="15.4" highway="18.4"/>
                </ad:consumptions>
                <ad:cost-model>
                   <ad:fuel-price value="1.75" />
                   <ad:power-price value="0.45" />
                   <ad:consumption-costs value="1234" />
                   <ad:consumption-price-year value="2024" />
                   <ad:tax value="234" />
                   <ad:time-frame from="2024" till="2027"/>
                 <ad:co2-costs>
                   <ad:low base-price="45" accumulated="2345" />
                   <ad:middle base-price="55" accumulated="3345" />
                   <ad:high base-price="65" accumulated="4345" />
                 </ad:co2-costs>
                </ad:cost-model>
                ...
            <ad:specifics>
            ...
        
    

Example Ad Detail Response with new values (New XML)

        
            GET /search-api/ad/123 HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/vnd.de.mobile.api+xml
            ...
            <ad>
                ...
                <range>455</range>
                <equivalentAllElectricRange>48</equivalentAllElectricRange>
                <emissions>
                    <combined>
                        <co2>23</co2>
                        <co2Class>B</co2Class>
                    </combined>
                    <discharged>
                        <co2>123</co2>
                        <co2Class>D</co2Class>
                    </discharged>
                </emissions>
                <consumptions>
                    <weightedCombinedFuel>4.8</weightedCombinedFuel>
                    <weightedCombinedPower>10.5</weightedCombinedPower >
                    <fuel>
                        <combined>4.4</combined >
                        <city>5.4</city >
                        <suburban>4.0</suburban >
                        <rural>4.2</rural >
                        <highway>6.4</highway >
                    </fuel/>
                    <power>
                        <combined>14.4</combined >
                        <city>12.4</city >
                        <suburban>13.4</suburban >
                        <rural>15.4</rural >
                        <highway>18.4</highway >
                    </power/>
                </consumptions>
                <costModel>
                    <fuelPrice>1.75</fuelPrice>
                    <powerPrice>0.45</powerPrice>
                    <consumptionCosts>1234</consumptionCosts>
                    <consumptionPriceYear>2024<consumptionPriceYear>
                    <tax>234</tax>
                    <timeFrame>
                        <from>2024</from>
                        <till>2027</till>
                    </timeFrame>
                    <co2Costs>
                        <low>
                            <basePrice>45</basePrice>
                            <accumulated>2345</accumulated>
                        </low>
                        <middle>
                            <basePrice>55</basePrice>
                            <accumulated>3345</accumulated>
                        </middle>
                        <high>
                            <basePrice>65</basePrice>
                            <accumulated>4345</accumulated>
                        </high>
                    </co2Costs>
                </costModel>
                ...
            </ad>
            ...

        
    

The following fields are deprecated and will be removed after 90 Days starting from 29th of April, so it is advised to switch to the above newly introduced fields

        
        

            ...
            <emission-fuel-consumption>
                ...
            </emission-fuel-consumption>
            <wltp-values>
                ...
            </wltp-values>
            ...
        
        
    

Affected Interfaces: Search-API Ad-Stream

26.03.2024 New data fields for PKW EnVKV 2024

From around CW16 (15.04.-21.04.) it will be possible to submit the full set of newly required consumption and emission values according to the new PKW-EnVKV released in Feb 2024.

The new values can be derived from the label on energy consumption and CO2-emissions provided by the manufacturer of the car.

New according to the new PKW EnVKV means:

- ads with condition “NEW”
OR
- ads with condition “USED” AND (mileage <= 1000 km OR firstRegistration <= 8 months ago)

As we only have the first registration month, we calculate firstRegistration month + 8 months to determine if the data is required.
Example: First registration 01/2024: Data is required for this listing even if the current month is September (09).

The following table describes which fields are required for each car depending on its fuel type:

The following table describes costs related fields which are required for each car, but are not dependent on its fuel type:

Example request with new values (Petrol car):

        
            POST /seller-api/sellers/12/ads HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/vnd.de.mobile.api+json
            {
                "mobileAdId": "226083",
                "mobileSellerId": "1224",
                "creationDate": "2024-03-21T11:01:39+01:00",
                "modificationDate": "2024-03-21T11:01:39+01:00",
                "vehicleClass": "Car",
                "category": "SmallCar",
                "make": "AUDI",
                "model": "A4",
                "modelDescription": "Neuer A4",
                "condition": "NEW",
                "fuel": "PETROL",
                "cubicCapacity": 1545,
                "emissions": {
                    "combined": {
                        "co2": "86",
                        "co2Class": "C"
                    }
                },
                "consumptions": {
                    "fuel": {
                        "combined": "4.4",
                        "city": "5.4",
                        "suburban": "4.0",
                        "rural": "4.2",
                        "highway": "6.4"
                    }
                },
                "costModel": {
                    "fuelPrice": "1.75",
                    "consumptionCosts": "3234",
                    "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"
                    }
                },
                "countryVersion": "DE",
                "damageUnrepaired": false,
                "description": "",
                "deliveryDate": "2024-03-21T00:00:00+01:00",
                "price": {
                    "consumerPriceGross": "12345.00",
                    "type": "FIXED",
                    "currency": "EUR"
                }
            }
        
    

Example request with new values (Electric car):

        
            POST /seller-api/sellers/12/ads HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/vnd.de.mobile.api+json
            {
               "vehicleClass": "Car",
               "category": "SmallCar",
               "make": "VW",
               "model": "ID.3",
               "modelDescription": "ID.3",
               "condition": "NEW",
               "fuel": "ELECTRICITY",
               "range": 455,
               "emissions": {
                   "combined": {
                       "co2": 0,
                       "co2Class": "A"
                   }
               },
               "consumptions": {
                   "power": {
                       "combined": "14.4",
                       "city": "12.4",
                       "suburban": "13.4",
                       "rural": "15.4",
                       "highway": "18.4"
                   }
               },
               "costModel": {
                   "powerPrice": "0.45",
                   "consumptionCosts": "1234",
                   "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"
                   }
               },
               "countryVersion": "DE",
               "damageUnrepaired": false,
               "description": "",
               "price": {
                   "consumerPriceGross": "12345.00",
                   "type": "FIXED",
                   "currency": "EUR"
               }
            }
        
    

Example request with new values (Plugin Hybrid car):

        
            POST /seller-api/sellers/12/ads HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/vnd.de.mobile.api+json
            {
               "mobileAdId": "226083",
               "mobileSellerId": "1224",
               "creationDate": "2024-03-21T11:01:39+01:00",
               "modificationDate": "2024-03-21T11:01:39+01:00",
               "vehicleClass": "Car",
               "category": "SmallCar",
               "make": "AUDI",
               "model": "A6",
               "modelDescription": "Neuer A6 Plugin Hybrid",
               "condition": "NEW",
               "fuel": "HYBRID",
               "hybridPlugin": true,
               "cubicCapacity": 1345,
               "equivalentAllElectricRange": 48,
               "emissions": {
                   "combined": {
                       "co2": 23,
                       "co2Class": "B"
                   },
                   "discharged": {
                       "co2": 123,
                       "co2Class": "D"
                   }
               },
               "consumptions": {
                   "weightedCombinedFuel": "4.8",
                   "weightedCombinedPower": "10.5",
                   "fuel": {
                       "combined": "4.4",
                       "city": "5.4",
                       "suburban": "4.0",
                       "rural": "4.2",
                       "highway": "6.4"
                   },
                   "power": {
                       "combined": "14.4",
                       "city": "12.4",
                       "suburban": "13.4",
                       "rural": "15.4",
                       "highway": "18.4"
                   }
               },
               "costModel": {
                   "fuelPrice": "1.75",
                   "powerPrice": "0.45",
                   "consumptionCosts": "1234",
                   "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
                   }
               },
               "countryVersion": "DE",
               "damageUnrepaired": false,
               "description": "",
               "deliveryDate": "2024-03-21T00:00:00+01:00",
               "price": {
                   "consumerPriceGross": "12345.00",
                   "type": "FIXED",
                   "currency": "EUR"
               }
            }
        
    

The new fields validation will be introduced as followed:

1. New fields will be added so data can be sent. There will be no validation in the beginning (except checking for numeric values) to give time to adapt the listings. Please still make sure to send the required fields according to the new PKW EnVKV so listings can be shown as required legally.
2. On 29.04.24 we will enable a minimum validation, meaning all fields that are required to be shown on the mobile.de search result page (red fields in the overview table) will become mandatory dependent on the fuel type.

Affected Interfaces: Seller-API

19.03.2024 Leasing can be submitted as E-Bike feature

From the end of March 2024, registered dealers will have the ability to insert E-Bikes on our platform. As part of this, dealers can also choose whether they want to offer leasing for a certain listing.

Unlike Car leasing, it is not possible to enter leasing rates or any additional information during the initial phase.

To activate leasing for a certain listing, please include the following:

        
            "ebikeLeasing": {
                "active": true
            }
        
    

Disabling leasing can be done via:

        
            "ebikeLeasing": {
                "active": false
            }
        
    

Alternatively, omitting this element completely will also disable leasing.

This change is scheduled for release in production around CW 13, 2024.

Affected Interfaces: Seller-API

29.02.2024 E-Bikes can be searched via SearchAPI

From the end of March 2024, registered dealers will have the ability to search for E-Bikes on the Search-API. There is a new VehicleClass (EBike), new categories (CargoBike, FoldingBike, TrekkingBike, MountainBike, CityBike, CrossBike, RacingBike, FatBike, OtherEBike) and several query paramters to allow different criteria of searches.

Please note:

• The search endpoint will return basic information about the ad, for complete details use ad details endpoint.

New fields:

The following fields are also added to the Ad details endpoint for EBike ads

Example request XML:

        
            POST /search-api/ad/123 HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/xml

            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
            <ad:ad xmlns:resource="http://services.mobile.de/schema/resource"
                xmlns:ad="http://services.mobile.de/schema/ad"
                xmlns:financing="http://services.mobile.de/schema/common/financing-1.0"
                xmlns:leasing="http://services.mobile.de/schema/common/leasing-1.0"
                xmlns:seller="http://services.mobile.de/schema/seller" key="123"
                url="https://services.mobile.de/search-api/ad/123">
            .................
            <ad:vehicle>
                <ad:specifics>
                    .................
                    <ad:number-of-gears value="6"/>
                    <ad:frame-shape key="LOW_STEP" url="https://services.mobile.de/refdata/frameshapes/LOW_STEP">
                        <resource:local-description xml-lang="de">Tiefeinsteiger</resource:local-description>
                    </ad:frame-shape>
                    <ad:frame-material key="ALUMINIUM" url="https://services.mobile.de/refdata/framematerials/ALUMINIUM">
                        <resource:local-description xml-lang="de">Aluminium</resource:local-description>
                    </ad:frame-material>
                    <ad:battery-position key="INTEGRATED" url="https://services.mobile.de/refdata/batterypositions/INTEGRATED">
                            <resource:local-description xml-lang="de">Integrierter Akku</resource:local-description>
                    </ad:battery-position>
                    <ad:battery-manufacturer key="BOSCH" url="https://services.mobile.de/refdata/batterymanufacturers/BOSCH">
                        <resource:local-description xml-lang="de">Bosch</resource:local-description>
                    </ad:battery-manufacturer>
                    <ad:motor-position key="MIDDLE_MOTOR" url="https://services.mobile.de/refdata/motorpositions/MIDDLE_MOTOR">
                        <resource:local-description xml-lang="de">Mittelmotor</resource:local-description>
                    </ad:motor-position>
                    <ad:bike-suitable-for key="MALE" url="https://services.mobile.de/refdata/bikesuitablefor/MALE">
                        <resource:local-description xml-lang="de">Herren</resource:local-description>
                    </ad:bike-suitable-for>
                    <ad:bike-gear-type key="DERAILLEUR_GEARS" url="https://services.mobile.de/refdata/bikegeartypes/DERAILLEUR_GEARS">
                        <resource:local-description xml-lang="de">Kettenschaltung</resource:local-description>
                    </ad:bike-gear-type>
                    <ad:wheel-size value="18"/>
                    <ad:battery-capacity-wh value="500"/>
                    <ad:weight value="30"/>
                    .................
                </ad:specifics>
            </ad:vehicle>
            .................
            </ad:ad>

        
    

This change is scheduled for release in production around CW 13, 2024.

Affected Interfaces: Search-API

22.01.2024 E-Bikes can be inserted to mobile.de

From the end of March 2024, registered dealers will have the ability to insert E-Bikes on our platform. The insertion and management processes can be carried out within the dealer area and also via Seller-API as for other vehicle categories.

Please note:

• Export to Kleinanzeigen is not available for E-Bikes.
• During the initial phase, E-Bikes can only have condition = "NEW".

New fields:

The existing fields listed below will also be available for E-Bikes:

Autopanorama and Direct Offer are also available for E-Bikes.

Example request:

        
            POST /seller-api/sellers/12/ads HTTP/1.1
            Host: services.mobile.de
            Content-Type: application/vnd.de.mobile.api+json

            {
                "vehicleClass": "EBike",
                "make": "BUTCHERS AND BICYCLES",
                "modelDescription": "Some Description",
                "condition": "NEW",
                "category": "CityBike",
                "damageUnrepaired": false,
                "frameHeight": 35,
                "frameMaterial": "ALUMINIUM",
                "wheelSize": "27.5",
                "batteryCapacityWh": 600,
                "weight": 20,
                "numberOfGears": 6,
                "bikeGearType": "OTHER_GEAR_TYPE",
                "batteryManufacturer": "BOSCH",
                "bikeSuitableFor": "UNISEX",
                "motorPosition": "MIDDLE_MOTOR",
                "batteryPosition": "INTEGRATED",
                "frameShape": "LOW_STEP",
                "frameNumber": "TEST123",
                "exteriorColor": "BLACK",
                "manufacturerColorName": "schwarz",
                "price": {
                    "consumerPriceGross": "20498.94",
                    "vatRate": "19.00",
                    "type": "FIXED",
                    "currency": "EUR"
                },
                "description": "This is really a nice e-bike.",
                "dealerHomepage": true,
                "individualContactId": "64c232e9c19479425a9bb5c4",
                "nationalDelivery": {
                    "radius": 400,
                    "period": 90,
                    "fee": 50,
                    "additionalInformation": "Delivery via our service provider."
                }
            }
        
    

This change is scheduled for release in production around CW 13, 2024.

Affected Interfaces: Seller-API

11.12.2023 FTP Server address change for null-leasing.com

The FTP server for providing inventory data to null-leasing.com will change to ftp.null-leasing.com. From today on, the new FTP server can be used. The old server at the address null-leasing.exavault.com will still work in parallel until Jan 31, 2024. After that date, null-leasing.exavault.com cannot be used anymore to provide listing updates.

Furthermore, to increase data security, the new server will not support plain (unencrypted) FTP. Supported transport mechanisms are:

1. FTPS on port 21 (sometimes referred to as “FTP-SSL / Explicit AUTH TLS”, “Encryption: TLS/SSL Explicit” or “Explicit FTP over TLS”)
2. SFTP on port 22 (sometimes referred to as “SSH File Transfer Protocol”)

What needs to be done

1. Change the FTP server address to ftp.null-leasing.com
2. Make sure to use a supported secure transport mechanism (see above)

Note: Login data (username and password) is not affected by the server change.

Affected Interfaces: Seller-API

27.10.2023 New price type "LEASING_ONLY"

Around CW2 2024, we will introduce a new price type LEASING_ONLY for ads on mobile.de. As the name suggests, LEASING_ONLY ads do not have a buying option. They are only meant to be leased. The process of creating/updating an ad including leasing does not change:

1. Create an ad with the price type LEASING_ONLY using the /ads endpoint
2. Add leasing rates to the ad using the /leasing endpoint

• The price's VAT rate becomes mandatory in case of LEASING_ONLY. Thus, you also need to provide the consumerPriceNet. In case the VAT rate is missing, the error 'vat-rate-required-for-leasing-only' is returned. This error is not to be confused with the error 'leasing_ad_has_no_vat' here which is returned if leasing is added to a normal ad which does not have a VAT.
• The listing will not be visible to the consumer until leasing rates got added. Once leasing rates are added, the listing will be visible on the consumer side.
• For now it is not possible to change the price type of a LEASING_ONLY listing. If you try to change the price type, the error 'leasing-only-price-type-cannot-be-changed' is returned.
• Bookable features (demand tools) will, for this initial release, not be possible for LEASING_ONLY listings. If you add bookable features by accident to a LEASING_ONLY listing they will be ignored. We will inform you in another changelog entry, once it is possible.

        
          "price": {
            "type": "LEASING_ONLY",
            "consumerPriceNet": "17226.00",
            "vatRate": "19.00",
            "currency": "EUR"
          }
        
    

Affected Interfaces: Seller-API

11.09.2023 Battery certificate label for electric vehicles

Around CW38 we will add another label to the listings in order to support users with finding vehicles that have a battery certificate. To use it there are two steps to follow:

1. Upload the battery certificate as vehicle image. We suggest to upload it as the 2nd picture as not all users have a look at all pictures of the listing.

2. Insert the text that you see below as part of the vehicle description to make sure the vehicle is getting the label.

There will be no dedicated new field/document upload for the "Battery certificate" for now.

Please note that the label will be only shown for vehicles with fuel type : ELECTRICITY

Text that needs to be sent as part of the vehicle description: Das Fahrzeug verfügt über ein Batterie Zertifikat. Für weitere Informationen nehmen Sie bitte direkten Kontakt auf.

Affected Interfaces: Seller-API

04.09.2023 Launch of Direct Offer API

In CW 40 we will make the recently introduced feature "direct offers" also available via API. The direct offer feature allows dealers to contact potential customers who have shown interest in their inventory. On mobile.de, consumers can add interesting listings to their watchlist, known as the "Car park." Dealers can now observe this expression of interest within their records. Through the "Direct offer" feature, dealers can now anonymously reach out to these consumers by sending offers to those who have saved the listings on their watchlist. Consumers have the option to directly respond to these offers and communicate with the dealer through conventional channels such as email, chat, or phone calls. Please refer to the Direct Offer page for more information and documentation for technical specifications.

Furthermore, as part of launch of Direct Offer api, the settings section of retrieve a single seller is extended. The settings section now contains settings information related to direct offers. Please refer to the documentation for details.

Affected Interfaces: Seller-API

21.08.2023 New features bookable via API

From the beginning of October 2023 the SellerAPI will be extended to offer the booking of three new features that will become available as part of the new account offering. Depending on the account type of the dealer he will be able to use certain features. More details related to this can be found in the description of each new feature below.

Seller Endpoint adjustments

As part of adding new features we will extend the Seller endpoint
https://services.mobile.de/docs/seller-api.html#Seller_Resource
To provide information about the new features:

        
            ...
            "settings": {
            "maxImages": 30,
            "maxHighlights": 3,
            "maxIndividualConacts": 5, ← new, "0" if dealer is not eligible
            "maxMultiLocations": 10, ← new, , "0" if dealer is not eligible
            "nationalDelivery" : true, ← can be true or false
            "usedCarSeals": [
            "VW",
            ...
        
    

This information will be available when retrieving all Sellers and also when retrieving a single Seller. In addition, the endpoint for retrieving a single Seller will provide information about the new features within the invoiceItems and freeContingents.

        
         {
            ...
            "billingForecast": {
                "billingPeriod": "2023-11",
                "calculationDate": "2023-11-01",
                "invoiceLanguage": "de",
                "currency": "EUR",
                "invoiceItems": [
                {
                    "descriptor": "DELIVERY_OPTION",
                    ...
                },
                {
                    "descriptor": "MULTI_LOCATION",
                    ...
                },
            ...
                "freeContingents": [
                    {
                        "featureDescriptor": "DELIVERY_OPTION",
                        "description": "Fahrzeuganlieferung Umkreis",
                        "contingentUnlimited": "false",
                        "available": "15.0"
                    },
                    {
                        "featureDescriptor": "MULTI_LOCATION",
                        "description": "Fahrzeuganlieferung Standort",
                        "contingentUnlimited": "false",
                        "available": "30.0"
                    },
            ...
         }
        
    

Individual Contact

Individual Contact is a new feature that allows the dealer to have individual persons of contact (incl. individual E-Mail / Phone) assigned to each listing. This should allow the dealer to have a more personalised offer as the best contact can be directly mentioned in the listing.

The creation/management of the contacts must be done once in the dealer area. To set up a new individual contact the dealer needs to login and navigate to "My company --> External view". There is a new TAB "Individual contact" to configure new persons of contact.
The different contacts can also contain the same contact data for phone and/or mail and only different names/images if there is a central lead management system for example.

Based on the account type the dealer is allowed to create a certain amount of contacts:
Bronze: not included
Silver: 1
Gold: 5
Platinum: 10

The configured contacts can be retrieved via API. As part of this the API is also providing an ID for each contact that can be used to assign the contact to a specific listing. Once a contact is assigned all leads will be sent to the assigned individual contact (Calls and E-Mails). Each listing can only have one contact assigned at the same time. If no contact is assigned the main contact data (as per default) will be used.
New fields (only relevant for reading):

JSON example when reading all individual contacts of one Seller:

        
           https://services.mobile.de/seller-api/sellers/21127/individual-contacts
            [
                {
                    "individualContactId": "64c232e9c19479425a9bb5c4",
                    "firstName": "Max",
                    "lastName": "Muster",
                    "email": "max@mobile.de",
                    "jobTitle": "Salesagent",
                    "phone": {
                        "countryCallingCode": "49",
                        "areaCode": "030",
                        "number": "1234567890"
                    }
                },
                {
                    "individualContactId": "64ca1066312cd92e09108323",
                    "firstName": "Martha",
                    "lastName": "Muster",
                    "email": ",martha@mobile.de",
                    "jobTitle": "Manager",
                    "phone": {
                        "countryCallingCode": "49",
                        "areaCode": "045",
                        "number": "1234567890"
                    }
                }
            ]
        
    

JSON example when assigning an individual contact to an ad
(can be done as part of listings creation or via changing it afterwards):

        
           https://services.mobile.de/seller-api/sellers/21127/ads/207648
            {
                "mobileAdId": "207648",
                "mobileSellerId": "21127",
                "vehicleClass": "Car",
                "category": "Limousine",
                "make": "ALFA ROMEO",
                "model": "Giulia",
                ...
                "individualContactId": "64c232e9c19479425a9bb5c4"
            }
        
    

If the individualContactId is wrong the contact will be ignored and the ad is still created/updated.

Multi Location

Multi location is a new feature that allows dealers to show a listing on up to 10 additional locations in addition to the main location/account where the vehicle is inserted. This allows dealers to increase the reach of their listings as they can make it available in other regions also.
The listing is still only inserted once in mobile.de but would then have more than one location assigned.
The creation/management of the locations must be done once in the dealer area. To set up a new location the dealer needs to login and navigate to "My company --> External view". There is a new TAB "Locations" to configure new locations.
The Multi Location feature is only available for dealers within the Platinum account. These dealers can create up to 10 locations.

The configured locations can be retrieved via API. As part of this the API is also providing an ID for each location that can be used to assign the location to a specific listing. It is possible to assign up to 10 additional locations to one listing.
On the consumer side the listings will then have the information that they can be delivered to several other locations.
This is a paid feature. Please check the price list for further details.
New fields (only relevant for reading):

JSON example when reading all multi-locations of one Seller:

        
           https://services.mobile.de/seller-api/sellers/21127/multi-locations
            [
                {
                    "id": "64ca0bd5eda6a6578e2cfcb8",
                    "name": "My Location 1",
                    "deliveryOption": {
                        "period": 30,
                        "fee": "0"
                    },
                    "location": {
                        "street": "Am See",
                        "houseNumber": "2",
                        "zip": "67547",
                        "city": "Worms",
                        "country": "DE"
                    }
                },
                {
                    "id": "64ca0bb4eda6a6578e2cfcb7",
                    "name": "My Location 2",
                    "deliveryOption": {
                        "period": 14,
                        "fee": "50"
                    },
                    "location": {
                        "street": "Lechlweg",
                        "houseNumber": "1",
                        "zip": "83607",
                        "city": "Holzkirchen",
                        "country": "DE"
                    }
                }
            ]
        
    

JSON example when assigning multiple locations to an ad
(can be done as part of listings creation or via changing it afterwards):

        
           https://services.mobile.de/seller-api/sellers/21127/ads/207648
            {
                "mobileAdId": "207648",
                "mobileSellerId": "21127",
                "vehicleClass": "Car",
                "category": "Limousine",
                "make": "ALFA ROMEO",
                "model": "Giulia",
                ...
                "multiLocations": [
                    {
                        "id": "64ca0bd5eda6a6578e2cfcb8"
                    },
                    {
                        "id": "64ca0bb4eda6a6578e2cfcb7"
                    }
                ]
            }
        
    

If the multiLocations id is wrong the location will be ignored and the ad is still created/updated.

National Delivery

National Delivery is a new feature that allows dealers to show a listing up to Germany wide if they are able to deliver it in a certain radius. This allows dealers to increase the reach of their listings as they can make it available in other regions as well. On the consumer side the listings will then have the information that they can be delivered in a certain radius/Germany wide.

The National delivery feature is only available for dealers within the Platinum account.

This is a paid feature. Please check the price list for further details.

New fields:

JSON examples when booking the feature:

        
           https://services.mobile.de/seller-api/sellers/21127/ads/207648
            Free of charge:
            {
                "mobileAdId": "207648",
                ...
                "nationalDelivery": {
                    "radius": 600,
                    "period": 14,
                    "fee": "0",
                    "additionalInformation": "Some more details"
                }
            }
            Lump sum:
            {
                "mobileAdId": "207648",
                ...
                "nationalDelivery": {
                    "radius": 400,
                    "period": 90,
                    "fee": "50",
                    "additionalInformation": "Some more details"
                }
            }
            Germany wide:
            {
                "mobileAdId": "207648",
                ...
                "nationalDelivery": {
                    "period": 150,
                    "fee": "150",
                    "additionalInformation": "Some more details"
                }
            }

        
    

Affected Interfaces: Seller-API

10.07.2023 More parameters for leasing rates

New fields for leasing rates to break down the monthly costs of the leasing. All of them are optional. The change will be available in CW32.

            {
                ...
                rates:[{
                    ...
                    "maintenanceMonthlyCost": "10.00",
                    "wearMonthlyCost": "11.00",
                    "maintenanceAndWearCombinedMonthlyCost": "21.00",
                    "liabilityInsuranceMonthlyCost": "15.00",
                    "liabilityInsuranceDeductible": "200.00",
                    "fullyComprehensiveInsuranceMonthlyCost": "25.00",
                    "fullyComprehensiveInsuranceDeductible": "300.00",
                    "vehicleTaxMonthlyCost": "12.00",
                    "summerAndWinterTiresMonthlyCost": "50.00",
                    "tuevMonthlyCost": "22.00",
                    "returnInsuranceMonthlyCost": "15.00"
                }]
            }
        

Affected Interfaces: Seller-API

06.07.2023 New endpoints and attributes for Online Buying and Selling (OBS)

Around CW31 we will add new endpoints to the Seller API to support the business model “Online Buying and Selling” (short “OBS”). The business model requires the submission of detailed information on the vehicles’ condition as well as certain documents (e.g., car registration documents or speedometer photos). Via the new endpoints dealers participating in OBS will be able to enrich their existing classifieds listings (given by the mobileAdId) with the additionally needed OBS information. They will further be able to read, alter and delete previously submitted OBS information. The endpoints will use the already existing authentication of the Seller API.

Note: The newly introduced fields are optional. We encourage participating dealers and their contracted transfer service providers to submit as many details as possible. mobile.de maintains quality checks of all OBS listings and reserves the right to not publish listings if critical information is missing. Further details are communicated to the participating dealers during the onboarding for OBS and via the dealer usage agreement (“Händlernutzungsvereinbarung”) for OBS.

Note: API requests to the new endpoints will return a 403 error (“Forbidden”) when the dealer is not an OBS partner dealer.

Endpoint for handling OBS related files:
OBS related files are handled via multipart file upload. The roles for the files are given below:

Supported methods: POST, GET, DELETE, PATCH

Example Request to upload images or documents:

        
            curl -s -u AUTH 'https://services.mobile.de/seller-api/sellers/:mobileSellerId/ads/:mobileAdId/obs/media/DamageImages ' \
                -H 'accept: */*' \
                -H 'Content-Type: multipart/form-data' \
                -F 'files=@car1.jpeg;type=image/jpeg' \
                -F 'files=@audi.jpeg;type=image/jpeg'
        
    

The POST request returns a list of documents with URLs. These URLs need to be stored on the side of the transfer service provider or dealer to be able to reference documents for future requests.

To add a description to a damage image, make an additional PATCH call, as shown in the example below.

Example Request to add description to images:

        
            curl -s -u AUTH -X PATCH 'https://services.mobile.de/seller-api/sellers/:mobileSellerId/ads/:mobileAdId/obs/media/DamageImages ' \
                -H 'accept: */*' \
                -H 'Content-Type: application/json' \
                -d '[
                      {
                        "imageUrl": "oneUrl",
                        "description": "Informative description to the image"
                      }
                    ]'
        
    

Endpoint for handling OBS related data (other than files):

Supported methods: PUT, GET

Example Request:

        
            curl -s -u AUTH 'https://services.mobile.de/seller-api/sellers/:mobileSellerId/ads/:mobileAdId/obs/data ' \
                -H "Accept: application/vnd.de.mobile.api+json"
                '{
                  "noDamagesOrExcessiveTracesOfUse": true,
                  "vehicleCondition": "Fahrzeug ist in einem guten Zustand",
                  "rentalOrCarSharing": true,
                  "warrantyExpirationDate": "202306",
                  "pickupEarliestDate": "2023-07-30T09:05:12.494Z",
                  "optOutOfSellingThroughMobileDe": true,
                  "pickupTires": "WINTER",
                  "pickupContact": {
                    "firstName": "Max",
                    "lastName": "Mustermann",
                    "role": "Operations",
                    "email": "max.mustermann@maxmustermann.de",
                    "phoneNumber": "1234556",
                    "mobileNumber": "1234556"
                  },
                  "pickupAddress": {
                    "companyName": "Autohaus Mustermann GmbH",
                    "street": "Albert-Einstein Ring",
                    "houseNumber": "1",
                    "city": "Kleinmachnow",
                    "zipCode": "14532",
                    "note": "Bitte an der Rezeption melden."
                  }
                }'
        
    

Affected Interfaces: Seller-API

29.06.2023 Technical changes in Lead emailing

UTF-8 encoding for Lead emailing
To support a wider range of characters, our core lead emails will in future be encoded in UTF-8 character encoding.

Lead management systems or systems who automatically process Mobile.de emails need to expect the emails to be encoded in ISO-8859-1 OR UTF-8. Please use standard Content-Type headers of the email to detect the source encoding.

Content-Type: text/plain; charset=utf-8

Images not send attached to every email
To reduce bandwith, Mobile.de lead emails will in future reference images via public urls instead of attaching the images as part of the email.

Before:

-----=_Part_12...
Content-Type: image/png; name=logo.png
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename=logo.png
Content-ID: <logo.png>
    

After:

<a src="https://static.classistatic.de/mobilede-logo.png"/>>
    

No HTML compaction
The HTML part of Mobile.de lead emailing will no longer be send compacted.

Before:

<body><table><tr><td><strong>Enquiry about your vehicle</strong></td></tr></table>/body>

After:

<body>
    <table>
        <tr>
            <td><strong>Enquiry about your vehicle</strong></td>
        </tr>
    </table>
</body>

More information about Mobile.de lead emailing can be found here.

Affected Interfaces: Leads

01.06.2023 Umweltbonus Label for electric vehicles

Around CW23 we will add another label to the listings in order to support the last change for the user to make an advantage of the "Umweltbonus". (German Government Grants.) Only if the following text is send as part of the vehicle description, the listing will get the "Umweltbonus" Label.
There will be no dedicated new field for the "Umweltbonus" for now.

Please note that the label will be only shown for vehicles with fuel type : ELECTRICITY

Text that needs to be send as part of the vehicle description:
Das angebotene Fahrzeug ist gemäß der Liste der förderfähigen Elektrofahrzeuge, abrufbar auf der Seite des BAFA, für den Umweltbonus als finanzielle Unterstützung für Käufer von Elektrofahrzeugen berechtigt.

Affected Interfaces: Seller-API

01.06.2023 Rebranding of ebay-kleinanzeigen to Kleinanzeigen

Due to the naming change of ebay-kleinanzeigen to Kleinanzeigen the SellerAPI will be adjusted. The changes will happen around CW27 (from 03.07.)

The following things will be changed:

The API changes will happen in the following steps:

1. CW27 (from 03.07.)
New keys/values will be available for listing creation/update. For a certain time (about 4 weeks) the API will still accept the old keys/values as part of listing creation/update and map them. When reading listing, seller and billing data the new keys/values will already be send as part of the data.

2. CW31 (from 31.07.)
Mapping will be removed so that always the new keys/values must be send. Otherwise the call will be rejected.

Affected Interfaces: Seller-API

15.03.2023 New car attributes for electric vehicles

Around CW15, we will add new attributes for cars in order to support the better insertion of e-cars. As part of this, we will also add new search options so that these vehicles can be better found. All new fields are optional but it is highly recommended to fill them in order to make sure vehicles are found.
Please note that the new properties can only be sent for the following fuel types: ELECTRICITY and HYBRID / HYBRID_DIESEL with hybridPlugin=true.

            {
                ...
                "vehicleClass": "Car",
                "fuel": "ELECTRICITY",
                ...
                "chargingTime": 330,
                "chargingTimeFast": 150,
                "plugTypes": [
                    "TYPE_1",
                    "CCS_COMBO"
                ],
                ...
            }
        

This change will be released in CW 15/2023

Affected Interfaces: Seller-API

08.03.2023 New error in Seller API leasing.

We introduced a new error in the leasing part of the Seller API. When the price of an ad has no VAT set, it is not possible to offer leasing. In this case we return the error leasing_ad_has_no_vat Make sure to set the VAT first.

Affected Interfaces: Seller-API

23.02.2023 Ad-Stream clean up

On 1.11.2022 we announced to remove outdated fields in the search-api and ad-stream. This cleanup will now be applied to all other output formats like for instance json.

            {
                ...
                 "daytimeRunningLights": true,
                ...
            }
        

            <ad>
                ...
                 <daytimeRunningLights>true</daytimeRunningLights>
                ...
            </ad>
        

Please refer to the 2018 attributes description and Data Format Reference for more details.

This change will be released in KW 15/2023

Affected Interfaces: Ad-Stream

19.12.2022 Remove leasing restriction for default rate and rate limit

The legacy restriction to require a default private rate with 10.000km annual mileage when creating a leasing offer was lifted. From now on at least one rate private or commercial is required for creating a leasing offer.
At the same time the limitation to have a minimum/maximum number of leasing rates was removed. Any number of rates can now be created by a dealer. The related leasing settings will be removed from Seller Settings Schema end of February.

Affected Interfaces: Seller-API

01.11.2022 Search-API/Ad-Stream clean up

We plan to introduce two changes in the search-api and ad-stream.

1. The format of the dealer homepage url will change.

   • Now: https://home.mobile.de/SMOKE
   • After the change: https://home.mobile.de/home/redirect.html?customerId=1234



Please refer to the "homepage" element in the xsd schema for more details.
The new url is semantically the same, so no changes are required on the client side software. This change will go live in the next couple of days without any further announcement.

2. In 2018 we introduced a number of new attributes that allow better description of a vehicle. Now as part of the api clean up we plan to remove some outdated fields that were replaced by these new attributes. The deprecated fields are part of the features list, e.g.

        <ad>
            ...
            <vehicle>
                ...
                <features>
                    <feature key="PARKING_SENSORS" />
                    ...
                </features>
            </vehicle>
        </ad>
    

Deprecated Features	Replacement
CRUISE_CONTROL	speed-control attribute
ADAPTIVE_CRUISE_CTL	speed-control attribute
TUNER	radio attribute
DAYTIME_RUNNING_LIGHTS	daytime-running-lamps attribute
BENDING_LIGHTS	bending-lights-type attribute
XENON_HEADLIGHTS	headlight-type attribute
TRAILER_COUPLING	trailer-coupling-type attribute
SLIDINGDOOR	sliding-door-type attribute
MP3_INTERFACE	number of infotainment related features: SOUND_SYSTEM, VOICE_CONTROL, TOUCHSCREEN, USB, CARPLAY, ANDROID_AUTO, INTEGRATED_MUSIC_STREAMING
PARKING_SENSORS	parking-assistants attribute
LEATHER_SEATS	interior-type attribute
ROOF_BARS	ROOF_RAILS feature
E10	E10_ENABLED feature

Please refer to the 2018 attributes description and xsd schema for more details.

This change will be released on 13.12.2022

Affected Interfaces: Search-API/ Inseratsschnittstelle Ad-Stream

30.03.2022 Support of WLTP in Search-API/Ad-Stream

Retrieving WLTP values on the affected interfaces will be available today. Please refer to the change log entry for more details regarding WLTP.

Affected Interfaces: Search-API/ Inseratsschnittstelle Ad-Stream

25.03.2022 Old eBay image URLs are not working anymore

As part of the switch to Adevinta we also changed our image URLs. We saw that there are cases where it seems that the old eBay picture URL is still stored on data provider side.
This leads to the situation that in case of an image/ad update, the old image URL is sent to us. When this happens, the image on mobile.de site gets lost because the eBay image URL is not working anymore.

If you still have eBay image URLs stored within your database, you should do the following:

1. Option (preferred)

   conciliate pictures URLs by a GET request for the ad and by comparing the image md5 hash sums (they did not change)

2. Option

   re-upload all pictures and store the new URL/references

After doing so, you should not have any eBay picture URLs connected to the listings anymore.

Please avoid resending all the vehicle images per default.

Examples:
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

If not already done, this should happen as soon as possible to avoid losing images.

Affected Interfaces: Seller-API

16.02.2022 Support of WLTP in Search-API/Ad-Stream

The xsd schema for the Search-API and Ad-Stream is now extended with the WLTP values. Please refer to the change log entry for more details regarding WLTP. The actual change in the APIs to provide the new fields will be added after 16.03.2022 and be announced in a separate change log entry.

Affected Interfaces: Search-API/ Inseratsschnittstelle Ad-Stream

06.12.2021 Support of WLTP (Worldwide harmonized Light Duty Test Procedure)

Starting in September 2018, alle passenger cars need to be registered with WLTP values. EnVKV was still based on NEDC values, requiring car manufacturers to recalculate WLTP values to NEDC valus. Although a renewed EnVKV based on WLTP has been promised since 2019 and was announced again for Q4 2021, we do not see new government regulations coming until later in 2022. As more and more car models only come with WLTP consumption values, we have decided to allow the insertion of EnVKV required cars with only WLTP values. We are still asking everybody to insert an EnVKV compliant vehicle with NEDC values. Only if these values do not exist, you will be able to insert vehicles with WLTP values. For all vehicle types except plugin hybrids and electric vehicles we are asking you to send the following data

• Combined fuel consumption (in l/100km, kg/100km)
• Combined CO2 emission (in g/100km)

For electric vehicles we are asking for

• Electric Range in km
• Combined power consumption in kWh/100km
• Combined CO2 emission (in g/km)

For plugin hybrids we are asking for

• Weighted combined fuel consumption in l/100km
• Weighted combined power consumption in kWh/100km
• Weighted Combined CO2 emission in g/km
• Electric Range in km

Changes will be effective as of 05.01.2022, see WLTP Values for details. We are going to support WLTP in Search-API and Ad-Stream too. Schema changes will be announced soon.

Affected Interfaces: Seller-API

19.11.2021 Change of image section within all APIs showing image data

As part of the switch to Adevinta we will also change our images URLs. This change is done in steps as we need to prepare / change some things in regards to images sizes and data we can provide.

In the future it will not be possible to create image URLs for different sizes on your own using a baseURL + parameter, as the image URL will be fully different for different sizes of the same image.

These are the changes:

1. Base URL will be removed from SellerAPI in CW01 2022

   We will remove the baseURL as in the future every image size will have its own URL. The “ref” field remains. It should be used as identifier for an image while creating or updating ads. This change is going to happen CW01 2022.

   Data Example:

   {
       "images": [
           {
               "ref": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f8-dcca-4c7f-ba2b-5f50942b713b?rule=mo-640.jpg",
               "hash": "fda8487ed7fcfbecdf1eb55cf582fccf"
           },
           {
               "ref": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-640.jpg",
               "hash": "fda8487ed7fcfbecdf1eb55cf552fcdf"
           }
       ]
   }
   

2. Search API / AdStream (legacy xml) will get additional image sizes in CW01 2022

   We will add different images sizes:

   size="XXL" 1024 x 768
   size="XXXL" 1600 x 1200

   During this change image URLs themself will not change. If you have created the URLs on your own, knowing the parameters you have to add, you must now switch to use the URLs we provide for each given size.

   The schema of KPI-API/AdStream/Search-API has been already adjusted!

   Data Example:

   <ad:image>
       <ad:representation size="ICON" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-80.jpg"/>
       <ad:representation size="S" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-200.jpg"/>
       <ad:representation size="M" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-240.jpg"/>
       <ad:representation size="L" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-360.jpg"/>
       <ad:representation size="XL" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-640.jpg"/>
       <ad:representation size="XXL" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1024.jpg"/>
       <ad:representation size="XXXL" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1600.jpg"/>
   </ad:image>
   
   <seller:logo-image>
       <seller:representation size="ICON" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-80.jpg"/>
       <seller:representation size="S" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-200.jpg"/>
       <seller:representation size="M" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-240.jpgG"/>
       <seller:representation size="L" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-360.jpg"/>
       <seller:representation size="XL" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-640.jpg"/>
       <seller:representation size="XXL" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1024.jpg"/>
       <seller:representation size="XXXL" url="https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1600.jpg"/>
   </seller:logo-image>

3. AdStream json data format will change in CW01 2022

   Ad images: The baseUrl and ref fields will be removed. Fields to the Urls with specific images sizes will be added.

   "images": [
       {
           "baseUrl": "img.classistatic.de/api/v1/mo-prod/images/46/467621f9-acce-1d7f-ca2b-9f13912d713b?rule=eps_",
           "ref": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-640.jpg",
           "hash": "6861736831",
           "icon": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-80.jpg",
           "s": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-200.jpg",
           "m": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-240.jpg",
           "l": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-360.jpg",
           "xl": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-640.jpg",
           "xxl": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1024.jpg",
           "xxxl": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1600.jpg"
       }
   ]

   Dealer logo The dealerLogoBaseUrl field will be replaced with dealerLogo.

   "dealerLogoBaseUrl": "img.classistatic.de/api/v1/mo-prod/images/46/467621f9-acce-1d7f-ca2b-9f13912d713b?rule=eps_",
   "dealerLogo": {
           "icon": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-80.jpg",
           "s": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-200.jpg",
           "m": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-240.jpg",
           "l": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-360.jpg",
           "xl": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-640.jpg",
           "xxl": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1024.jpg",
           "xxxl": "https://img.classistatic.de/api/v1/mo-prod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1600.jpg"
   }
   

4. URLs will be switched to the new image service for SellerAPi, SearchAPI and AdStream in Q1 2021

   During this change the URLs will be switched. For SearchAPI and AdStream some image sizes will change slightly as the new service is not providing all sizes exactly as before.

   Change of sizes:
   “M” 298 x 244 to 240 x 180
   “L” 400 x 300 to 360 x 270

   We will announce upfront when this change will happen. Currently that's planned somewhen in Q1. When you made the changes from 1. and 2. this should not have such an effect anymore.

   Data example:

   <ad:image>
         <ad:representation size="ICON" url="https://img.classistatic.de/api/v1/mo-nonprod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-80.jpg"/> 
         <ad:representation size="S" url="https://img.classistatic.de/api/v1/mo-nonprod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-200.jpg"/> 
         <ad:representation size="M" url="https://img.classistatic.de/api/v1/mo-nonprod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-240.jpg"/> 
         <ad:representation size="L" url="https://img.classistatic.de/api/v1/mo-nonprod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-360.jpg"/> 
         <ad:representation size="XL" url="https://img.classistatic.de/api/v1/mo-nonprod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-640.jpg"/> 
         <ad:representation size="XXL" url="https://img.classistatic.de/api/v1/mo-nonprod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1024.jpg"/> 
         <ad:representation size="XXXL" url="https://img.classistatic.de/api/v1/mo-nonprod/images/46/467621f9-dcca-4c7f-ba2b-5f50942b713b?rule=mo-1600.jpg"/> 
   </ad:image>

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle KPI-API Ad-Stream

14.09.2021 Change of addition of new energy efficiency classes

According to new government regulation, there are two additions to the energy efficiency classes, A++ and A+++. It is possible to upload listings with these new energy efficiency classes starting Friday 17.09.2021.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle Ad-Stream

03.08.2021 Change of employee cars

It is now possible to upload employee cars with an age of up to 23 months.

Affected Interfaces: Seller-API

09.06.2021 KPI API historical data availability changed to 30 days due to data privacy reasons

Due to data privacy reasons historical ad data availability will be changed to 30 days from 01.07.2021 (instead of 45 days currently).

Affected Interfaces: KPI-API

12.06.2020 VAT change from 19% to 16% from 1st July 2020

From 1st July 2020, Germany will reduce VAT from 19% to 16%. mobile.de will not automatically set the 16%.

Please also take this into account when entering vehicle data and adjust the value-added tax (VAT) rate or prices accordingly to our Price Schema.

Affected Interfaces: Seller-API

26.05.2020 Launch leasing information to listings

Adding leasing information to ads is possible starting today as a beta product. Please refer to the documentation for details. mobile.de dealer will be informed in the near future about this new functionality.

Affected Interfaces: Seller-API

10.01.2020 New calculation of free contingents as of February 1st 2020

The free contingents for Top Ad, Page-1-Ad and Eyecatcher for users of the Comfort- and Premium-Package will be recalculated in the future. From Feb. 1st 2020, the number of free contingents a dealer receives will be based on the average number of ads listed over the last three active months. In this way it can be ensured which monthly free contingent the dealer has available. If the dealer have had an account for less than three months, we will calculate the average based on the three previous month's activity. Before, the free contingent was determined from the inventory of the respective month and was therefore very variable. Now the monthly free contingent is already fixed at the beginning of the month and can be optimally planned.

Affected Interfaces: Seller-API

18.12.2019 Launch of new API sandbox environment

A new API sandbox is now available at https://sandbox.services.mobile.de and is ready for testing the API integration. The old sandbox will be switched off in January 2020. Please refer to the documentation for details.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle

25.11.2019 Launch of "mobile.de Rating-API"

Managing ratings of a dealer by API is available from today. Please refer to the documentation for details.

Affected Interfaces: Seller-API

25.09.2019 Removal of deprecated data format, removal of deprecated feature booking method, removal of token authentication, introduction of dealer Rating-API

Some deprecated features/functionalities will be removed from our APIs on 09.12.2019. Furthermore we will introduce a "mobile.de Rating-API" which will allow you to manage dealer ratings.

1. Removal of deprecated XML data format in CW50 (09.12. - 15.12.)

   All requests made in old XML data format will be rejected and responses will be exclusively delivered in new data format. In case you are still using the old data format documented here you have to switch to the officially supported data format documented here.

   Doing this you also make sure that you are able to use all the newly introduced functionalities like retrieving vehicle price rating information prior creating the ad.

2. Deprecated bookedAdFeatures field will be removed in new data format CW50 (09.12. - 15.12.)

   In order to ensure a consistent feature booking the deprecated field bookedAdFeatures will be removed in the new data format. If you are still using the bookedAdFeatures field please switch to the more flexible bookableFeatures element.

   Please refer to our documentation and the corresponding changelog entry from 11.08.2017 for more details.

   The old XML data format is not affected as the new feature booking is not available there. Nevertheless, we will remove the old dataformat as communicated above.

3. Token authentication will be removed CW50 (09.12. - 15.12.)

   As already marked in the deprecated documentation, we will remove the token authentication in Seller-API. If you are still using a token or username/password as token please switch to the "HTTP basic authentication". In order to get a password (The username is your API user name) please contact datenpartner@team.mobile.de.

   All other authentication methods will be removed.

4. New endpoints for managing dealer ratings of connected dealers starting beginning Q4 2019

   As a longer requested functionality we will introduce the possibility to manage ratings of a connected dealer via Seller-API. In case the dealer has activated the permission in his account (active by default) you will be able to retrieve ratings, answer on ratings and trigger a rating. The new API will cover the complete functionality from the current page inside the mobile.de dealer area. As a dealer using the Seller-API on your own you will also be able to manage your dealer ratings. In this case the permission is granted in general.

   There will be a separate changelog entry and details in the Seller-API documentation soon (please check again in a few days).

Affected Interfaces: Seller-API

31.07.2019 TLS 1.0 will no longer be supported from 01.10.2019

From 01.10.2019 we will discontinue support for TLS 1.0 because of security reasons. Please make sure that your applications are updated.

If you are not updating, you will not be able to use any of the mobile.de APIs any longer.

In case you are a dealer registered on mobile.de and you are either sending vehicles to us using Seller-API or showing vehicles on your own homepage using the "Inseratseinbindung" please contact the person or company that created this integration for you to make sure it gets updated.

This change affects all services under our domain services.mobile.de: including Seller-API, Search-API (also "Inseratseinbindung"), KPI-API, Ad-Stream and Reference Data

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle KPI-API Ad-Stream

30.07.2019 Ad changes will be rejected in case uploadSticky is active

From 01.10.2019 onwards, Seller-API will respect the uploadSticky feature and reject any ad changes when the flag is set to true. In this case ad changes can only be done via the mobile.de dealer area.

The majority of the ads should not be affected and our recommendation is still to not do any ad changes in dealer area when having a transfer service provider. But as there are cases where not every function is 100% supported we made this functionality active again.

Affected Interfaces: Seller-API

11.07.2019 Used car seals changes

The following used car seals are available again: "Mercedes Benz Junge Sterne" and "Jung@Smart".

For available seals check: https://services.mobile.de/refdata/sites/GERMANY/classes/Car/usedcarseals

In order to use the mentioned used car seals, the customer needs to have a mobile.de premium account. For further details please ask your customer to contact his mobile.de contact person.

Affected Interfaces: Seller-API

05.06.2019 Additional field for seller resource

A new field in the seller resource describes if a seller uses additionally a picture provider for autopanorama or vehicle images. This information can be useful for Transfer Service Providers, who support sellers with external picture providers.

The additional field is only visible in case there exists a picture provider for the seller.

curl -s -u AUTH 'https://services.mobile.de/seller-api/sellers/:mobileSellerId' -H "Accept: application/vnd.de.mobile.api+json"
{
  {
    ...
    "type": "DEALER",
    "siteId": "GERMANY",
    "readonly": false,
    ...
    "pictureProvider": {
      "autopanorama": true,
      "images": false
    }
}

This field is also added to the old xml data format see seller-2.0.xsd.

Affected Interfaces: Seller-API

22.05.2019 Change to validation rules for fuel type HYDROGENIUM

From CW 22 on, we'll change fuel type HYDROGENIUM as follow:

• The unit for fuel type HYDROGENIUM will be kg/100km (was l/100km before)
• CO2 Emission will be a non-negative number (was positive before)

Please refer to the Fuel And Energy Consumption Validation Rules for details.

Affected Interfaces: Seller-API

16.05.2019 The "closedDomain" feature in Seller-API will be removed.

The closedDomain feature will removed in the Seller-API. In the initial phase the create and update ad calls will be changed so that, it will not be possible to enable the feature anymore, i.e. sending "closedDomain": true will be ignored.

The ads with the closedDomain feature active at the moment will stay that way unless deactivated by the user.

The change will be effective from 17.06.2019.

Affected Interfaces: Seller-API

13.05.2019 Reference data for modelrange and trimline is available

Now reference data for modelrange and trimline is available. Using reference data for trimline and modelrange describes the vehicle better and can result in better price ratings. Further details at reference data documentation.

Affected Interfaces: Seller-API

06.05.2019 Preview price rating information via Seller-API

Now price ratings can be previewed via a new Seller-API endpoint, before the ad has been created. The new endpoint is described in section Preview ad price rating of the Seller-API documentation. Price rating prediction is only working for the new data format (xml+json).

Affected Interfaces: Seller-API

13.02.2019 Used car seals changes

The following used car seals are not available any longer and were also removed from the reference data: "Mercedes Benz Junge Sterne" and "jung@smart". For available seals check: https://services.mobile.de/refdata/sites/GERMANY/classes/Car/usedcarseals

Dealer permissions were removed for the following used car seals and may be available later again:

• BMW
• MINI
• RENAULT
• MASERATI

Affected Interfaces: Seller-API

21.12.2018 EnVkV rules for electric vehicles with range extender changed

To ensure these vehicles can be inserted correctly we introduced a change to the EnVkV validation for electric cars with the range extender.

For the mentioned vehicle type this means, in case EnVkV values are required the following fields have to be send:

• consumptionCombined in l/100km
• consumptionPowerCombined kwh/100km
• co2 must be >0

Affected Interfaces: Seller-API

27.09.2018 Launch of mobile.de Auto-Panorama

The Auto-Panorama functionality in Seller-API is available from today. Please refer to the documentation for details.

Affected Interfaces: Seller-API

21.09.2018 Extended functionality for Auto-Panorama in Seller-API

The Seller-API has now GET calls in order to retrieve information about Auto Panorama.

Please refer to the documentation of the calls get interior and get exterior to learn more how to use them.

Affected Interfaces: Seller-API

21.09.2018 Deprecated fields in Seller API

The following fields are deprecated and will be ignored by Seller-API starting from 15.11.2018:

Replacement attributes:
        ...
    <vehicle:features>
      <vehicle:feature key="E10_ENABLED"/>
      <vehicle:feature key="ROOF_RAILS"/>
    </vehicle:features>
        ...
    <vehicle:specifics>
     	<vehicle:parking-assistants>
       		<vehicle:parking-assistant key="REAR_SENSORS"/>
		</vehicle:parking-assistants>
      	<vehicle:speed-control key="CRUISE_CONTROL"/>
      	<vehicle:radio>
        	<vehicle:radio-type key="TUNER"/>
      	</vehicle:radio>
      	<vehicle:daytime-running-lamps key="DAYTIME_RUNNING_LIGHTS"/>
      	<vehicle:sliding-door-type key="SLIDING_DOOR_RIGHT"/>
      	<vehicle:headlight-type key="XENON_HEADLIGHTS"/>
      	<vehicle:bending-lights-type key="BENDING_LIGHTS"/>
      	<vehicle:trailer-coupling-type key="TRAILER_COUPLING_FIX"/>
    </vehicle:specifics>
        ...

Please have a look on how to use the replacement fields in the Seller-API documentation and new features and attributes .

Fields are also marked as deprecated in the reference data: i.e. https://services.mobile.de/refdata/classes/Car/features

    <reference:item key="BENDING_LIGHTS" url="http://services.mobile.de/refdata/classes/Car/features/BENDING_LIGHTS" deprecated="true">
        <resource:local-description xml-lang="de">Kurvenlicht</resource:local-description>
    </reference:item>

Affected Interfaces: Seller-API

07.09.2018 Create Ad call in Seller-API is now idempotent

A new feature has been added to the Seller-API to make the POST new ad call idempotent.

It prevents duplicated ads being created when the call is retried after a failure. Please refer to the Seller-API documentation for details.

Affected Interfaces: Seller-API

30.08.2018 Launch of mobile.de Auto-Panorama: Final specification of endpoints for uploading 360° picture

The Auto-Panorama functionality in Seller-API is coming soon.

A final version of the api specification is already defined. Please refer to the documentation for details. To make the api more robust we have changed the specification comparing to the one in the changelog entry from 17.07.2017.

To allow you starting the integration work, this functionality is already available on the API Sandbox.

Affected Interfaces: Seller-API

31.07.2018 Update: Length of vehicle description field changes from 3000 to 5000 characters

Affected immediately, vehicle descriptions on mobile.de can have up to 5000 characters. When retrieving a vehicle using one of our APIs it may also contain up to 5000 characters.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle Ad-Stream

17.07.2018 Launch of mobile.de Auto-Panorama: New endpoints for uploading 360° pictures from September on

From beginning of September 2018 there will be two new endpoints available in SellerAPI to upload your existing 360° pictures. The implementation will support uploading one 360° picture per vehicle for an interior and a series of JPG images where the 360° outside view will be generated from.

Both endpoints support PUT and DELETE. In case a 360° picture/picture series is already uploaded it will be replaced when there is a new upload.

• Interior picture: 2:1 ratio .jpg image
• Exterior view: Up to 60 pictures as .jpg picture series

360° picture series uploaded via API will not be stabilized. The generated 360° picture will be shown in the standard "mobile.de Auto-Panorama" Player.

Please note:
It could occur that details of this announcement may change as we are still working on the implementation. Of course we try to avoid this, since we are interested in making your effort as small as possible. In case of necessary changes we will inform you in detail.

Exterior/Walkaround:
https://services.mobile.de/seller-api/sellers/:mobileSellerId/ads/:mobileAdId/car-panorama/exterior
Content-Type: multipart/form-data

Interior:
https://services.mobile.de/seller-api/sellers/:mobileSellerId/ads/:mobileAdId/car-panorama/interior
Content-Type: image/jpeg

Affected Interfaces: Seller-API

13.07.2018 Update: Length of vehicle description field changes from 3000 to 5000 characters

Support for 5000 characters in vehicle description field is still work in progress and we're aiming for a release in CW 30. As soon as the change is live, we'll publish a new entry in the changelog.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle Ad-Stream

05.07.2018 New vehicle attributes will be added as Search-API parameters

Recently added attributes and features are also added to the Search-API so they can be used for queries. Within the detail page they were added already some time ago.

Affected Interfaces: Search-API / Inseratsschnittstelle

26.06.2018 Length of vehicle description field changes from 3000 to 5000 characters

Within the next days we will enhance the vehicle description field from 3000 to 5000 characters. As soon as the change is live you are able to send vehicle descriptions with up to 5000 characters and when retrieving a vehicle using one of our APIs it may also contain up to 5000 characters.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle Ad-Stream

17.04.2018 New attributes available for Cars in our APIs and on mobile.de

Seller-API and Search-API now support new features and attributes for the vehicle-type "Car". In addition some existing attributes will also be available for other categories.

The List of new features and attributes including the glossary can be found here: new features and attributes.

In case of any technical questions please contact the mobile.de customer service.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle

12.04.2018 Ad Turbo forecast and trial contingent information in Seller-API

Starting from around CW 16, Seller-API will provide additional details about Ad Turbo forecast (paid bookings) and trial period in seller resource when using our JSON data format.

GET https://services.mobile.de/seller-api/sellers/12

{
  "mobileSellerId": "12",
  "customerNumber": "8",

  ...

  "trialPeriods": [
    {
        "bookableFeature": "adTurbo",
        "freeTries": "10",
        "trialPeriodStart": "2018-04-01T10:00:00Z"
        "trialPeriodEnd": "2018-04-30T10:00:00Z"

    }
  ]
}

Affected Interfaces: Seller-API

28.03.2018 New attributes will be added in April

Instead of previously announced, our new attributes will be added mid of April 2018.

Please see the following table for an overview of new features and attributes.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle

28.03.2018 Enhanced image upload

The image upload functionality in the seller-api has been extended with the new endpoints:

1. Upload image independently from ad creation.
2. Associate uploaded images with ads using json/xml payload.

Additionally the Create ad endpoint has been extended to accept images so that new ads could be created with images.

The main benefit of the new functionality is to avoid problematic multipart requests and to give the users more granular control for error handling. Please refer to the seller-api documentation for more details.

Affected Interfaces: Seller-API

28.03.2018 Deprecated bookedAdFeatures field will be removed in new data format

In order to ensure a consistent feature booking the deprecated field bookedAdFeatures will be removed from June 2018 in the new data format. If you are still using the bookedAdFeatures field please switch to the more flexible bookableFeatures element.

Please refer to our documentation and the corrosponding changelog entry from 11.08.2017 for more details.

The old XML data format is not affected as the new feature booking is not available there. Nevertheless, we suggest switching to the new data format (XML/JSON).

Affected Interfaces: Search-API / Inseratsschnittstelle

28.03.2018 Token authentication will be removed

As already marked in the documentation, we will remove the token authentication in Seller-API. If you are still using a token or username/password as token please switch to the "HTTP basic authentication".

All other authentication methods will be removed beginning June 2018.

Affected Interfaces: Seller-API

28.03.2018 Sandbox support limited to main APIs

In order to ensure that main services are running in our sandbox, we'll limit the sandbox capabillities to our main APIs. From now on the sandbox will support the main Seller-API and Search-API usecases, meaning it's possible to create and read ads and upload pictures using the Seller-API.

Other functions like the mobile.de dealer area and public search/vehicle detailpages are not maintained/supported actively. In order to check if an ad was created as expected please use the Seller-API to compare the ad after creation/update.

For the future we will investigate if we can find another more reliable solution in order to support general mobile.de usecases even in our sandbox.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle

09.03.2018 Added glossary for new attributes

In order to support you in explaining our new features / attributes we added a glossary to the HTML file mentioned in the respective changelog entry.

The List of features including the glossary can be found here: new features and attributes.

Affected Interfaces: Seller-API

09.03.2018 Various vehicle data fields will be removed

Together with adding new attributes also some existing fields will be cleaned up as they are deprecated. The following fields will be removed from beginning June 2018:

Affected Interfaces: Seller-API

20.03.2018 XML schema with new vehicle attributes released

As previously announced, our XML schema for Search-API has been updated with new vehicle attributes.

Please have a look at the Ad Data XSD to see new attributes in the vehicle detail page from Search-API.

Affected Interfaces: Search-API / Inseratsschnittstelle

01.03.2018 New attributes added soon

Around mid/end of March 2018 we will add new features and attributes for existing vehicles categories. All attributes will be added to the vehicle-type "Car". In addition some existing attributes will also be available for other categories.

Please see the following table for an overview of new features and attributes.

Our recommendation is to start with the area "Extended Attributes for Cars" as these changes will affect already existing attributes and may affect existing applications.

None of the new fields is mandatory so not sending them is not leading to an error response. For the beginning the new attributes and features will only be shown on the vehicle detail page on mobile.de and in our Search-API.

A glossary with more details regarding new attributes will be published in the following weeks.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle

01.03.2018 eBayK-Feature booking not possible on ad-creation anymore in the future

From beginning April 2018 it is not possible anymore to book the ebayK feature (ebaykExport) on ad creation. The reason for this is, that the ad must fulfill some criterias to be valid for the ebayK export. One criteria is that it must have at least one image. At the moment picture upload is not possible on ad creation.

In order to book the ebayK feature please create the ad first, upload one or more pictures and then book the ebaykExport feature. In case you are sending the ebayK feature on ad creation in the future will will "ignore" the booking and send a warning. The ad will be created without the ebayK feature then.

Affected Interfaces: Seller-API

15.02.2018 Ad Turbo available in Seller API and Dealer area

As announced the new demand tool Ad Turbo is available now. You can find some important details below:

• The new feature can be tested in a cost free trial phase from 15.02.2018 – 31.03.2018.
• The Ad Turbo can only be booked by Comfort & Premium dealers with a dealer rating of at least 3.5 stars.
• Dealers will receive an individual free contingent based on their inventory in January. Please find details on the Ad Turbo landing page.
• Within the trial period there is no booking possibility beyond the free contingent.
• The unbooking of activated Ad Turbos via the SellerAPI is not possible during the trial period. After the trial period the feature can be booked/unbooked as usual.

Please recommend dealers to directly contact our Sales-Team to get a booking recommendation for the Ad Turbo: 030/ 81097-940.

Further details can be found on our Ad Turbo landing page.

Affected Interfaces: Seller-API

19.01.2018 New mobile.de demand tool available mid of February 2018

Mid of February 2018 we will introduce a new demand tool “Ad Turbo” for Premium and Comfort dealers. It can be booked using the Seller-API the following ways.

{
    "mobileAdId": "123456",

    ... obmitted for brevity

    "bookableFeatures": {
        "adTurbo": {
            "active": true
        }
    }
}

<seller-ad:ad id="123456">
    ... obmitted for brevity

    <seller-ad:mobile-features>
        <seller-ad:feature>AD_TURBO</seller-ad:feature>
    </seller-ad:mobile-features>
</seller-ad:ad>

There will be a trial period until end of March 2018. During this period the "Ad Turbo" can only be booked but NOT unbooked using the SellerAPI to avoid that free bookings are lost.

Within the trial period dealers are getting a limited amount of free "Ad Turbo" bookings and an active "Ad Turbo" is valid for the complete ad lifetime or until it gets unbooked manually via the dealer area. All active "Ad Turbo" bookings will be deactivated at the end of the trial period to avoid unexpected costs. After the trial period the tool will be billed as usual (per vehicle/per day).

More details regarding this specific tool will be send out to all eligible dealers mid of February.

Affected Interfaces: Seller-API

09.11.2017 REMINDER - Upload API to be switched off starting end of September 2017

Affected Interfaces: Upload-Interface (CSV / XML)

23.10.2017 Pricerating Information in Search-API

Starting in November 2017, the Search-API will provide Price Rating Information for Ads. The information will be added to the detail view and can be retrieved a few seconds after the ad was created. In case it has not yet been calculated, no such information will be provided.

<price-rating>
    <label key="GOOD_PRICE"/>

    <label-ranges>
        <label-range key="VERY_GOOD_PRICE" from="10012" to="10023"/>
        <label-range key="GOOD_PRICE" from="10023" to="10045"/>
        <label-range key="REASONABLE_PRICE" from="10045" to="100766"/>
        <label-range key="INCREASED_PRICE" from="100766" to="1003453"/>
        <label-range key="HIGH_PRICE" from="1003453" to="1012455"/>
    </label-ranges>
</price-rating>

If you have any technical questions, please contact mobile.de customer service.

Affected Interfaces: Search-API / Inseratsschnittstelle

21.08.2017 Automatic ebayK export - changed maximum price for Cars

End of CW35 the maximum price for cars that are included in the automatic ebayK export for Comfort and Premium customers will be raised to 15.000€ (from 12.000€). This is not affecting any external API directly. So normally no change is needed.

In case you are using this limit in your software to advise your customers regarding the manual ebayK export there may be a need to adapt the content.

Affected Interfaces: Seller-API Upload-Interface (CSV / XML)

21.8.2017 Price Valuation information in Seller API

Starting around end of September 2017, the SellerAPI will provide Price Rating Information for Dealer Ads. The information will be added to a sub resource of an ad and can be retrieved using a GET Request a few seconds after the ad was created.

In case it has not yet been calculated, no such information will be provided.

The new sub resource will be:

https://services.mobile.de/seller-api/sellers/:mobileSellerId/ads/:mobileAdId/price-rating

{
    "label": "labelname"
}

{}

Please be aware that this information is only available using the new data format.

If you have any technical questions, please contact mobile.de customer service.

Affected Interfaces: Seller-API

11.08.2017 More flexible feature booking and additional feature details in Seller API

"bookableFeatures": {
  "topOfPage": {
    "active": true,
    "blocked": true,
    "reason": "BOOKING_ASSISTANCE"
  },
  "redPencil": {
    "active": true
  },
  "eyeCatcher": {
    "active": false,
    "blocked": true,
    "reason": "COST_CONTROL"
  }
...
...
... # All features incl. Status listed here
}

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

{
  "warnings": [
    {
      "key": "restricted-feature",
      "args": [
        {
          "key": "reason",
          "value": "BOOKING_ASSISTANCE"
        },
        {
          "key": "feature",
          "value": "topOfPage"
        },
        {
          "key": "active",
          "value": "true"
        }
      ]
    }
  ]
}

{
  "bookingAssistant": {
    "topOfPage": {
      "mobileAdIds": [12345, 5324, 54564, 56456546, 45645]
    },
    "eyeCatcher": {
      "mobileAdIds": [4535, 768768, 231342, 45646]
    }
  },
  "costControl": {
    "topOfPage": {}
  }
}

Affected Interfaces: Seller-API

10.07.2017 Upload API to be switched off starting end of September 2017

Affected Interfaces: Upload-Interface (CSV / XML)

30.05.2017: Feature bookings/unbookings will be ignored in case a feature was booked from booking buddy starting end CW22

Affected Interfaces: Seller-API Upload-Interface (CSV / XML)

27.04.2017: Possibility to insert vehicles in commercial vehicle classes with price on request

Affected Interfaces: Seller-API Upload-Interface (CSV / XML)

15.03.2017: Seller-API provides contingent information and some billing relevant details

Affected Interfaces: Seller-API

16.02.2017: additionalConditions - new free text field for describing financing conditions

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle Upload-Interface (CSV / XML) Ad-Stream

01.12.2016: Field top of page mobile is not supported anymore

Affected Interfaces: Seller-API Upload-Interface (CSV / XML)

23.11.2016: Highlights - additional fields describing an ad

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle Upload-Interface (CSV / XML) Ad-Stream

11.10.2016: Seller-API supports creating upload credentials

Affected Interfaces: Seller-API

29.07.2016: Seller-API supports the unified data format.

Affected Interfaces: Seller-API

21.07.2016: Field exhaust inspection is not supported anymore

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle Upload-Interface (CSV / XML) Ad-Stream

14.07.2016: Feature roofbars is not supported anymore

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle

28.06.2016: External dataformats (Czekalla, EVA-XML, Schwacke, SilverDAT) are no longer accepted for upload

Affected Interfaces: Upload-Interface (CSV / XML)

20.06.2016: Number of allowed images for an Ad

Affected Interfaces: Upload-Interface (CSV / XML) Seller-API

01.06.2016: FTP Upload Server replaced by HTTPS endpoint

Affected Interfaces: Upload-Interface (CSV / XML)

01.12.2015: New authentication mechanism for the Seller-API

Affected Interfaces: Seller-API

11.09.2015: Update of csv upload report with information about quality blocked / deleted ads

...
<adConversionReport>
	<deletedByMobileQuality>
		<reason>INCORRECT_DEALERPRICE</reason>
		<secondReason>DAMAGED_VEHICLE</secondReason>
	</deletedByMobileQuality>
	<eyeCatcher>false</eyeCatcher>
	<financingFeature>false</financingFeature>
	<internalId>a5358</internalId>
	<newlyCreated>false</newlyCreated>
	<otherWarning>
		<code>ad-blocked</code>
		<options/>
	</otherWarning>
	<recordNumber>3</recordNumber>
	<renewed>false</renewed>
	<topInCategory>false</topInCategory>
	<topOfPage>false</topOfPage>
	<uploadSticky>false</uploadSticky>
</adConversionReport>
...

...
<adConversionReport>
	<blockedByMobileQuality>
		<reason>INCORRECT_DEALERPRICE</reason>
	</blockedByMobileQuality>
	...
	<otherWarning>
		<code>ad-blocked</code>
		<options/>
	</otherWarning>
	...
</adConversionReport>
...

Affected Interfaces: Upload-Interface (CSV / XML)

20.08.2015: New search-api parameters

Affected Interfaces: Search-API

01.07.2015: Energy efficiency class mandatory for EnVKV compliant vehicles

Affected Interfaces: Seller-API Upload-Interface (CSV / XML)

01.07.2015: Financing Offer

Affected Interfaces: Seller-API Upload-Interface (CSV / XML)

27.04.2015: Search parameter interiorType replaces feature=LEATHER_SEATS

Affected Interfaces: Search-API / Inseratsschnittstelle KPI-API

01.03.2015: XML namespace in Seller-API

Affected Interfaces: Seller-API

01.03.2015: XML namespace in Upload-Interface

Affected Interfaces: Upload-Interface (CSV / XML)

10.02.2015: Changed KPI-API URLs

Affected Interfaces: KPI-API

10.02.2015: Changed Search-API URLs

Affected Interfaces: Search-API / Inseratsschnittstelle

01.02.2015: Pictures in upload

Affected Interfaces: Seller-API Upload-Interface (CSV / XML)

01.02.2015: Deleting images in Seller-API

Affected Interfaces: Seller-API

26.01.2015: Changed reference data URLs

Affected Interfaces: Search-API / Inseratsschnittstelle Ad-Stream KPI-API Seller-API Upload-Interface (CSV / XML)