API uitfaseringen

Tijdslijn voor de afschaffing van onze v1 API.

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/streetNumber is the intended replacement for both /v2/suggest/x/streetNumberAndPremise and v2/suggest/x/premise, which are now deprecated. Deprecated on 2022-11-14. The deprecated functions will be removed at 2025-01-01.

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

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.

Timeline

  • From now until 30 September 2026

    • All HTTP and HTTPS endpoints will continue to work as usual.

  • Starting 1 October 2026

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

Affected Endpoints

The following files and endpoints are currently accessible via HTTP and will be impacted by this change:

  • /v1.[1-9]/.*
  • /v1/.*
  • /v2/openapi.*
  • /clientaccesspolicy.xml
  • /static.*
  • /crossdomain.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.