Changelog

Show entries for:

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:

Deprecated field Replacement field
includedDeliveryCosts
mp3Interface
roofBars roofRails
parkingSensors parkingAssistants.REAR_SENSORS
cruiseControl speedControl.CRUISE_CONTROL
tuner radio.TUNER
daytimeRunningLights daytimeRunningLamps.DAYTIME_RUNNING_LIGHTS
slidingDoor slidingDoorType.SLIDING_DOOR_RIGHT
xenonHeadlights headlightType.XENON_HEADLIGHTS
bendingLights bendingLightsType.BENDING_LIGHTS
trailerCoupling trailerCouplingType.TRAILER_COUPLING_FIX
Legacy XML only
E10 E10_ENABLED
This change affects also the old xml data format: i.e.
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.

Uploaded pictures must fulfil the following criteria:

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.

Endpoints:
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.

The new data about trial periods will look like:
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:

Deprecated field Replacement field
includedDeliveryCosts
mp3Interface
roofBars
parkingSensors parkingAssistants.REAR_SENSORS
 
Legacy XML only
E10 E10_ENABLED
 
New attributes
cruiseControl speedControl.CRUISE_CONTROL
tuner radio.TUNER
daytimeRunningLights daytimeRunningLamps.DAYTIME_RUNNING_LIGHTS
slidingDoor slidingDoorType.SLIDING_DOOR_RIGHT
xenonHeadlights headlightType.XENON_HEADLIGHTS
bendingLights bendingLightsType.BENDING_LIGHTS
trailerCoupling trailerCouplingType.TRAILER_COUPLING_FIX

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:

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.

JSON data format
{
    "mobileAdId": "123456",

    ... obmitted for brevity

    "bookableFeatures": {
        "adTurbo": {
            "active": true
        }
    }
}
XML data format
<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

On 15.11.2017 we will switch off the Upload API and the possibility to directly upload files through the dealer area. The Seller API will remain the only way to insert vehicles besides the manual form on mobile.de. A notification was sent out already a few weeks ago to any active interface user. In case it is not possible for you to switch your application to use the SellerAPI you may switch to a Service Provider, use the mobile.de Dealer Area or AutoAct for managing your inventory.

This step is needed due to increased traffic and complexity during the last years/months.

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

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.

The information when shown for an ad will look like:
<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

The information when retrieving the endpoint for an ad will look like:
{
    "label": "labelname"
}
Price rating information is not available
{}

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

Through the introduction of the booking assistant a few weeks ago and the new cost control option in the near future, it will be the case that a feature booking/unbooking is rejected.

Starting around CW33, the Seller-API will get an additional resource for feature bookings.

This new resource will also provide more details about the current feature status of an ad and more flexibility with feature bookings.

New "bookableFeatures" resource when retrieving ads/an ad:
"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
}
How to book features using the new resource:
"bookableFeatures": {
  "topOfPage": {
    "active": true
  },
  "eyeCatcher": {
    "active": false
  }
}

NOTE: Features not included when creating/updating an ad will not be affected. The old status will still be in effect. This is not possible at the moment. Furthermore, we will have backward compatibility initially. This means that if the "old" feature booking resource is active, this will control the features. Also the response after creating/updating an ad will be supplemented with additional information in the event a feature change was not successful. The ad-data-change will be processed as usual and the response may contain a warning if, for example, the cost control is reached and a booking could not be made.

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

Additionally a new endpoint will be available to retrieve some additional seller information

Endpoint: https://services.mobile.de/seller-api/sellers/{seller-id}/feature-settings
{
  "bookingAssistant": {
    "topOfPage": {
      "mobileAdIds": [12345, 5324, 54564, 56456546, 45645]
    },
    "eyeCatcher": {
      "mobileAdIds": [4535, 768768, 231342, 45646]
    }
  },
  "costControl": {
    "topOfPage": {}
  }
}

At the beginning you will only receive warnings in case the booking assistant is controlling a specific feature that you try to book/unbook as the cost control is not active yet. From around end of September there will be the first cases where a booking is rejected with a warning because the dealer has activated the cost control for a specific feature.

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

Affected Interfaces: Seller-API

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

Starting on 30.09.2017 we will switch off the Upload API and the possibility to directly upload files through the dealer area. The Seller API will remain the only way to insert vehicles besides the manual form on mobile.de. A notification was sent out already a few weeks ago to any active interface user.

This step is needed due to increased traffic and complexity during the last years/months.

Please find your shutdown dates according to your contract below:

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

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

In case the booking buddy has booked a feature (TOP_OF_PAGE, EYE_CATCHER, PAGE_ONE_AD) any feature changes (booking//unbooking) will be ignored for this specific feature. All other features will be handled as usual for the specific ad.

There will be an Seller-API change in the near future to reflect this in the response after updating an ad. As soon as technical details are clear we will send out a communication.

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

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

From now on it is possible to insert vehicles with price on request instead of entering a price. This affects the following vehicle classes:

In order to insert a vehicle with price on request please specify as follows:

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

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

Please see seller resource for further details.

Affected Interfaces: Seller-API

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

This includes Seller-API, Search-API, Upload-Interface (CSV / XML) and Ad-Stream. Please refer to the documentation of the specific interface for more details.

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

The field top of page mobile is not supported anymore for upload interfaces. This includes Seller-API and Upload-Interface (CSV / XML).

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

23.11.2016: Highlights - additional fields describing an ad

The highlights are short free text remarks describing the ad. Depending on the account type (upcoming change in the beginning of the 2017) a dealer can specify a different number of highlights. Please refer to the documentation of the specific interface for more details.

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

11.10.2016: Seller-API supports creating upload credentials

Using the Seller-API it is possible now to create, delete and read upload credentials for assigned dealers in order to use these credentials for managing the inventory. This is especially needed for offline installed tools from service providers. Please see here for further details.

Affected Interfaces: Seller-API

29.07.2016: Seller-API supports the unified data format.

The Seller-API supports now the unified data format with the first class json support and simplified xml model.

A refreshed version of the Seller-API is now available here. The previous version of the documentation is still available here.

Affected Interfaces: Seller-API

21.07.2016: Field exhaust inspection is not supported anymore

The field exhaust inspection (AU) is not supported anymore for upload interfaces and retrieving interfaces. This includes Seller-API, Search-API, Upload-Interface (CSV / XML) and Ad-Stream.

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

14.07.2016: Feature roofbars is not supported anymore

Insertions of and searching by roofbars are not possible anymore.

Affected Interfaces: Seller-API Search-API / Inseratsschnittstelle

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

It is no longer possible to upload external dataformats (Czekalla, EVA (Volkswagen XML-Format), Schwacke (autoWert, SalesAssist und schwackeNET), SilverDAT II).

Affected Interfaces: Upload-Interface (CSV / XML)

20.06.2016: Number of allowed images for an Ad

The number of allowed images may vary for different sellers and should be retrieved using the relevant Seller-API resource. At the moment the number of images is still 15 but the api users are advised to not rely on that fixed number any more and refresh the seller settings periodically.

Please refer to the Seller-API and/or Upload-Interface (German / English) documentation for more details.

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

01.06.2016: FTP Upload Server replaced by HTTPS endpoint

Our Upload-FTP server is replaced by an HTTPS endpoint and will be switched off by end of 2016. Nothing is changed except the way that the upload file is transported to us (HTTPS instead of FTP). But consider switching to Seller-API anyway.

Please check out the Upload-Interface documentation (German / English) for more details.

Affected Interfaces: Upload-Interface (CSV / XML)

01.12.2015: New authentication mechanism for the Seller-API

The Seller-API now supports the HTTP Basic Authentication in addition to the existing Token authentication. It uses the same user credentials as the FTP Upload-Interface.

Please check out the Seller-API documentation (Authorization / permissions section) for more details.

Affected Interfaces: Seller-API

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

Starting today, we will inform our users in csv upload reports about ads, which are blocked or deleted from our quality team. Ads, which are blocked would need to be updated with a dealer to comply with our ad guidelines. Deleted ads need to be deleted by a dealer before it is possible to recreate these ads (this behavior is similar to the approach in our dealer area).

The XML upload report will be appended with the following information for a deleted ad:

...
<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>
...

The XML upload report will be appended with the following information for a blocked ad:

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

Note. The old indicator of blocked or deleted ads (element otherWarning/code:ad-blocked) will be removed by the end of the year.

Affected Interfaces: Upload-Interface (CSV / XML)

20.08.2015: New search-api parameters

The following new search parameters have been added

Please check out the Search-Api documentation for more details.

Affected Interfaces: Search-API

01.07.2015: Energy efficiency class mandatory for EnVKV compliant vehicles

The change has the following semantic:

When
the vehicle is EnVKV compliant (csv - 95/CR/envkv; xml - vehicle-1.0.xsd/envkv-compliant)

Then
the field 'energy efficiency class' (csv - 169/FN/energy_efficiency_class; xml - vehicle-1.0.xsd/energy-efficiency-class) must be specified.

More information about these fields is available in:

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

01.07.2015: Financing Offer

class="changecontent">

We are offering you the possibility to exclude the payment protection insurance (csv - 162/FG; xml - seller-ad-1.1.xsd/rate-insurance) from the financing offer. This makes it possible to send the following values to the interfaces:

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

Only if uploading XML, not for CSV:

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

This is just a reminder, nothing new: We are supporting only RGB color space images in all our upload interfaces it is not possible to upload CMYC images to our plattform.

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

01.02.2015: Deleting images in Seller-API

Just an advice, nothing new:

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)


Impressum / Imprint