The current CIF username / password combination will be replaced by an API key in the SOAP API calls. This API key should be added into the header of your API requests.
You can also fill in the API key in the former password field and send the same SOAP requests as you did before.
Deprecate support for TLS 1.0
TLS 1.0 is no longer considered strong cryptography and therefore cannot be used as a security control. For the PostNL API platform we will deprecate support for TLS 1.0 on September 6th 2018. After this change the clients that connect to the API proxies using TLS 1.0 or older (SSL) will not work anymore.
For more information see the News page.
The PostNL API’s are constantly being improved and enhanced with new products and functionalities. PostNL expects users to regularly upgrade their versions of the APIs, so they are always using a supported version of the integrated services. Some older versions have not been migrated to the new platform. Users of these APIs will therefore be obliged to update the outdated version(s).
In the API Manager you will find information of which APIs are currently linked to your API account. This is based on the use of the CIF web services. If an asterisk (*) is displayed next to the version of the API, then you are not using the most recent version. It is recommendable to migrate to the latest version but this is not necessary. If you currently use a version/versions that will cease to be operational, the most recent version will be shown next to the API name.
Documentation and Versioning of the API’s can be found on the Documentation pages of the Parcels API’s.
Note: An update will be required if you want to use the latest version of the APIs. This will entail programming a number of changes/new fields. See the versioning paragraphs.
Location API version 2.0 | 2.1
If you are currently use the CIF Location version 2.0, you will see the 2.1 in the API Manager. No changes have been made in the request interface in the updated version (2.0 to 2.1) So please upgrade to the 2.1 version. The only changes that has been made is:
The Location Type has been extended with partner Location Codes in the response Location Code.
Timeframe API version 2.0 | 2.1
For example, the error message in CIF can be Value 'GetDeliveryDate.CutOffTimes.CutOffTime.Time' is not in the correct format 'Time', whereas for the new platform we specify the exact field like this: Value 'GetDeliveryDate.CutOffTimes.2.CutOffTime.Time' is not in the correct format 'Time'.