Changelog

2024-11-19

09:03:40

1.1.2093

Relocating the Search-API to new servers

Our service provider has announced a short-term maintenance work on the Search-API servers for Thursday, 2024-11-21.
An approximate 4-hour downtime is to be expected.
However, the Search-API is already available on other servers, which are not yet public.

On Tuesday, 2024-11-19, we will switch the well-known address https://api.ssis.de:8443/api to these new servers.

Please be prepared for this, as we do not plan to reverse the changes.

At the same time, the Search-API is now available via https://api.eln.de/api.

We ask you to use this new domain moving forward, as we will be removing the old one in the medium term. However, we will announce this with sufficient advance notice.

Affected interfaces:

2024-07-05

13:58:31

1.1.2075

Update on the PKW-EnVKV amendment

As part of the PKW-EnVKV amendment that recently came into force, we have made adjustments for you within the ELN Search API, which we would like to inform you about today.

As announced in the last API newsletter, we have retrofitted the missing fields. These include the necessary fields for electric and plug-in hybrid vehicle offers. But also other fields that are necessary to create all the different PKW-EnVKV labels.

You can now access the new fields.
You can also receive the previously blocked electric and plug-in hybrid offers from us again. However, the information that you would also like to receive these offers must be sent to the ELN Search API.

This is for your protection, otherwise you will issue offers that do not contain all the legally required information.
This means that you should first program the output of the new fields and then activate the return of the electric and plug-in hybrid offers.

All ELN partners who use the in-house ELN embedding can already offer these new cars to their end customers again. In order to make this option available to you and your ELN partners again via the ELN Search API, we have made the following adjustments for you:


1. New fields in the /details endpoint in the consumption category:

wltpCombinedEmission
WLTP CO2 emission combined. Integer in g/km (set to 0 for electric). In the case of plug-in hybrid, it is the CO2 emission with a discharged battery
wltpFuelConsumptionCombined
WLTP fuel consumption combined. in l/100km (for natural gas in kg/100km). In the case of plug-in hybrid, the fuel consumption combined with a discharged battery
wltpFuelConsumptionCity
WLTP fuel consumption city. in l/100km (for natural gas in kg/100km). In the case of plug-in hybrid, the fuel consumption city with a discharged battery
wltpFuelConsumptionSuburban
WLTP fuel consumption suburban. in l/100km (for natural gas in kg/100km). In the case of plug-in hybrid, the fuel consumption suburban with a discharged battery
wltpFuelConsumptionRural
WLTP fuel consumption country road. in l/100km (for natural gas in kg/100km). In the case of a plug-in hybrid, the fuel consumption on country roads with a discharged battery
wltpFuelConsumptionHighway
WLTP fuel consumption on the highway. in l/100km (for natural gas in kg/100km). In the case of a plug-in hybrid, the fuel consumption on the highway with a discharged battery
wltpCombinedCO2Class
WLTP CO2 class combined. (A, B, C, D, E, F or G) in the case of plug-in hybrid it is the CO2 class when the battery is discharged
wltpFueltype
WLTP engine drive type: possible values ​​'combustion', 'electric', 'fuel' or 'plug_in_hybrid'
wltpPowerConsumptionCombined
WLTP combined power consumption: in kWh/100km in the case of plug-in hybrid the combined power consumption in purely electric operation
wltpPowerConsumptionCity
WLTP inner city power consumption: in kWh/100km in the case of plug-in hybrid the inner city power consumption in purely electric operation
wltpPowerConsumptionSuburban
WLTP suburban power consumption: in kWh/100km in the case of plug-in hybrid the suburban power consumption in purely electric operation
wltpPowerConsumptionRural
WLTP rural road power consumption: in kWh/100km in the case of plug-in hybrid the rural road power consumption in purely electric operation Operation
wltpPowerConsumptionHighway
WLTP power consumption highway: in kWh/100km in the case of plug-in hybrid, the power consumption highway in purely electric operation
wltpAllElectricRange
WLTP electronic range: in kilometers in the case of plug-in hybrid, the electronic range EAER
wltpWeightedCombinedEmission
WLTP CO2 emissions weighted combined: integer in g/km
wltpWeightedCombinedPower
WLTP energy consumption fuel weighted combined: in l/100km (for natural gas in kg/100km)
wltpWeightedCombinedFuel
WLTP energy consumption electricity weighted combined: in kWh/100km
wltpWeightedCombinedCO2Class
WLTP CO2 class weighted combined: (A, B, C, D, E, F or G)
wltpConsumptionCosts
WLTP energy costs: in EUR, for 15,000 km Annual mileage
fuelpriceAvgYear
Fuel price: EUR/l or kg on annual average
powerpriceAvgYear
Electricity price: cent/kWh on annual average
consumptionPriceYear
Year information for the fuel and electricity price fields: in YYYY format
co2CostMiddleBaseprice
Average CO2 costs per tonne: EUR/t, over the next 10 years (15,000 km/year)
co2CostMiddleAccumulatedPrice
Average CO2 costs extrapolated: EUR, over the next 10 years (15,000 km/year)
co2CostLowBaseprice
Low CO2 costs per tonne: EUR/t, over the next 10 years (15,000 km/year)
co2CostLowAccumulatedPrice
Low CO2 costs extrapolated: EUR, over the next 10 years (15,000 km/year)
co2CostHighBaseprice
High CO2 costs per Ton: EUR/t, over the next 10 years (15,000 km/year)
co2CostHighAccumulatedPrice
CO2 costs extrapolated: EUR, over the next 10 years (15,000 km/year)
co2CostTimeFrameFrom
CO2 prices period from: in YYYY format
co2CostTimeFrameTill
CO2 prices period to: in YYYY format

a detailed list of the data types can be found here: https://api.ssis.de:8443/api/documentation/apidoc/de/ssis/eln/api/dto/vehicle/Consumption.html


2. Fields in the endpoint /details marked as deprecated:


consumptionCity
consumptionOutskirts
consumptionTotal
consumptionElectricity
co2Emission
co2Efficiency
energyCarrierCost
wltpSlow
is replaced by wltpFuelConsumptionCity
wltpMiddle
is replaced by wltpFuelConsumptionSuburban
wltpFast
is replaced by wltpFuelConsumptionRural
wltpVeryFast
is replaced by wltpFuelConsumptionHighway
wltpCombined
is replaced by wltpFuelConsumptionCombined
wltpEmission
is replaced by wltpCombinedEmission
wltpEfficiency
is replaced by wltpCombinedCO2Class


3. New fields in the /search endpoint to search for the new WLTP fields


wltpCombinedCO2Class
WLTP Combined CO2 Class (A, B, C, D, E, F, G)
wltpCombinedEmissionRange
Filtering on the given range for "WLTP CO2 emissions combined". The highest and lowest provided values ​​are used.


4. Fields in the /search endpoint marked as deprecated:


co2Efficiency
consumptionRange
wltpEfficiency
wltpEmissionRange


5. New switch in the endpoint /search:

includeWltpObligatorySecondStage
It is used to switch the WLTP / PKW-EnVKV critical new cars on and off. This is switched off by default and thus prevents the transfer of new cars younger than 8 months and with less than 1,000 km mileage in accordance with the new regulation.

In addition to the combustion engines that you can activate with includeWltpObligatory, this switch also includes the electric and plug-in hybrid offers.

The includeWltpObligatorySecondStage switch alone therefore includes all offers that are mandatory under the PKW-EnVKV.


Thanks to these adjustments in the ELN Search API, you now have all the currently possible parameters for the next step in implementing the WLTP / passenger car EnVKV innovations. As soon as you are sure that you have taken all the necessary fields into account, you can tell us with every request to the /search endpoint that you also want to receive the EnVKV-required vehicles.



REMINDER: Beware of the risk of legal warnings
We provide you with the legally relevant vehicle data via our API. In addition, we check the vehicle data sent to us for plausibility and completeness. If the test results are negative, we will block the corresponding vehicles.
You will find these vehicles in the internal ELN with the note "Vehicle does not meet the data quality requirements".
What we cannot check is whether you or your service provider also collect and correctly output all the required data that we provide via our API.
This can be particularly critical with regard to the requirements of the PKW-EnVKV. There is a risk that you will receive a legal warning if you violate the PKW-EnVKV.

We therefore ask you to always keep an eye on the legal conditions and requirements. A good and highly recommended source of information is the BVfK Bundesverband freier Kfz-Händler e.V..
You can find information about the association at www.bvfk.de. Membership of the BVfK is available at reduced rates for ELN participants.

2024-03-21

17:31:59

1.1.2049

Update on the PKW-EnVKV amendment

In the course of the amendment to the PKW-EnVKV, which recently came into force, we have made adjustments to the ELN Search API for you, which we would like to inform you about today.

You have probably already noticed that we have not offered any data records on new vehicles via the ELN Search API in the last few days. This was done to protect you from warnings due to the amendment to the EnVKV for passenger cars, which came into force at very short notice.

As of today, most of these vehicles are available to you again!
(Due to the insufficient data records for new hybrid vehicles, these are currently not yet allowed through to the ELN Search API. Further adjustments will be made as soon as we receive legally compliant data. We will inform you about this separately).



All ELN partners who use the in-house ELN embedding can already offer these new cars to their end customers again. In order to make this option available to you and your ELN partners again via the Search API, we have made the following adjustments for you:

1. new field in the endpoint /details: `wltpEfficiency`
Is used to output the CO2 energy efficiency class according to WLTP and is added to each fuel type in the `consumption` sub-area. All other WLTP-relevant fields can also be found here.
2. new switch in the /search endpoint: `includeWltpObligatory`
Used to switch the WLTP / PKW-EnVKV critical new cars on and off. Is switched off "by default" and thus prevents the transfer of new cars younger than 8 months and with less than 1,000 km mileage according to the new regulation.

Thanks to these adjustments in the ELN search api, you now have all currently possible parameters for the next step in the implementation of the WLTP / PKW-EnVKV innovations.
As soon as you are sure that you have taken all the necessary fields into account, you can send the parameter to the /search endpoint with every request that you would also like to receive the vehicles subject to EnVKV.


REMINDER: Beware of the risk of legal warnings
We provide you with the legally relevant vehicle data via our API. In addition, we check the vehicle data sent to us for plausibility and completeness. If the test results are negative, we will block the corresponding vehicles.
You will find these vehicles in the internal ELN with the note "Vehicle does not meet the data quality requirements".
What we cannot check is whether you or your service provider also collect and correctly output all the required data that we provide via our API.
This can be particularly critical with regard to the requirements of the PKW-EnVKV. There is a risk that you will receive a legal warning if you violate the PKW-EnVKV.

We therefore ask you to always keep an eye on the legal conditions and requirements. A good and highly recommended source of information is the BVfK Bundesverband freier Kfz-Händler e.V..
You can find information about the association at www.bvfk.de. Membership of the BVfK is available at reduced rates for ELN participants.

2024-02-15

14:55:53

1.1.2025

Documentation update

The following changes have been made to the API documentation:
- Swagger GUI: some updates to only show endpoints for embedded dealer vehicles
- Changelog: new changelog design implemented

2024-01-03

15:05:28

1.1.2014

Start of the new changelog

To support you in your work with this API, we will inform you about changes in this changelog (Link).
Unfortunately, some changes will render the existing code unusable. However, we will point this out in advance in the changelog.

To stay up to date, we recommend subscribing to the RSS feed.