We're actively developing new features on the v2 API. The v1 API receives only bug fixes and speed improvements.
API V1 Deprecation Policy
The v1 will still be supported to at least 2027-12-31, probably longer. The final timeline for this will be announced when the v2 API moves to production status.
API V2 Deprecations
While the v2 API doesn't have the stable or production status yet, we're treating it as such in the case of API changes.
While the v2 API isn't declared production status yet, expect a deprecation period of at least 6 months. When stable, we'll allow for a deprecation period of at least 36 months.
This is a list of deprecations:
/v2/suggest/x/streetNumberis the intended replacement for both/v2/suggest/x/streetNumberAndPremiseand/v2/suggest/x/premise, which are now deprecated. Deprecated on 2022-11-14. The deprecated functions will be removed at 2025-01-01.- The
latitudeandlongitudeparameters in the/v2/locator/*and/v2/reverse/*endpoints have been replaced bylatandlng. Deprecated on 2026-04-15. The deprecated parameters will be removed at 2027-04-15.
Deprecation Notice: TLS Deprecation
https://proxy.pro6pp.nl/ will remove support for TLS 1.0 and TLS 1.1 on the 1st of October 2026.
Timeline
-
From now until 30 September 2026
- Support provided for TLS 1.0 and TLS 1.1 on https://proxy.pro6pp.nl/.
-
Starting 1 October 2026
- Only TLS 1.2+ will be supported on both https://proxy.pro6pp.nl/ and https://api.pro6pp.nl/.
Deprecation Notice: HTTP URL Support
As part of our ongoing efforts to improve security and reliability, we are deprecating support for HTTP versions of our URLs.
We did not switch HTTP off on 1 October 2026 as announced. The new date is 16 March 2027, with three brownouts before it, so integrations that still use HTTP show up while there is time to fix them.
Timeline
-
Until 1 February 2027
- All HTTP and HTTPS URLs keep working as usual.
-
Brownouts
- During these windows, HTTP requests are redirected to HTTPS, as after the cutoff. This redirect is temporary, so nothing keeps redirecting once a window ends:
- Tuesday 2 February 2027, 10:00 to 11:00 CET
- Tuesday 16 February 2027, 10:00 to 14:00 CET
- Tuesday 2 March 2027, 09:00 to 17:00 CET
- During these windows, HTTP requests are redirected to HTTPS, as after the cutoff. This redirect is temporary, so nothing keeps redirecting once a window ends:
-
Starting 16 March 2027
- HTTP support will be permanently disabled for all URLs.
- Any HTTP traffic will be automatically redirected to HTTPS (using a permanent redirect).
- Only HTTPS will be supported moving forward.
Clients that do not follow redirects fail during the brownouts and after the cutoff, and so do SOAP calls and other POST requests, which a redirect turns into a GET.
Affected URLs
These URLs still answer over HTTP. Every other HTTP URL, including the rest of the v2 API, already redirects to HTTPS.
- The v1 API, including SOAP calls:
http://api.pro6pp.nl/v1/...,http://api.pro6pp.nl/v1.1/...and the later v1 versions - The SOAP WSDL files, such as
http://api.pro6pp.nl/v1/soap/api.wsdlandhttp://api.pro6pp.nl/v1.4/soap/api.wsdl - The v2 OpenAPI documents
http://api.pro6pp.nl/v2/openapi.jsonandhttp://api.pro6pp.nl/v2/openapi.yaml - Sample files under
http://api.pro6pp.nl/static/... http://api.pro6pp.nl/crossdomain.xmlandhttp://api.pro6pp.nl/clientaccesspolicy.xml
We strongly encourage all users to update their integrations to use HTTPS well before the cutoff date.
Next Steps for Users
- Review your applications, scripts, and services for any usage of
http://URLs. - Update all requests to use the secure
https://equivalents. - Test your integrations with HTTPS to ensure smooth operation before the deprecation date.
If you have any questions or need assistance, please contact our support team.
