The Dutch Postal Code Tracker API is designed to provide accurate validation and detailed lookup information for Dutch zip codes. With an emphasis on accuracy and reliability, this API enables developers to improve address validation processes and optimize postal code lookup functions for applications in the Netherlands.
By using the Dutch Postal Code Tracker API, users can ensure the accuracy of Dutch zip codes in their applications. The API leverages official datasets to perform comprehensive validation checks, confirming that postal codes conform to official formats and standards. This reduces input errors and improves both data quality and user experience.
In addition to its validation capabilities, the API offers extensive query capabilities for Dutch postal codes. Developers can access detailed information related to specific postal codes, such as city, municipality and province, which facilitates accurate validation and enrichment of addresses within applications.
In summary, the Dutch Postal Code Tracker API is an essential tool for improving address validation and streamlining zip code lookup in applications targeting the Netherlands. With its accurate validation, comprehensive lookup capabilities, real-time data access and ease of integration, the API ensures accurate and reliable postal code data for users.
It will receive a parameter and provide you with a JSON.
Basic Plan: 10 requests per second.
Pro Plan: 10 requests per second.
Pro Plus Plan: 10 requests per second.
Premium Plan: 50 requests per second.
To use this endpoint you must indicate a postcode and a house number in the parameters.
Address by post code and house number - Endpoint Features
| Object | Description |
|---|---|
postal_code |
[Required] Indicates a postal code |
house_number |
[Required] Indicates a house number |
{"province":"Noord-Holland","municipality":"Amsterdam","city":"Amsterdam","postal_code":"1011AJ","street":"Prins Hendrikkade","street_number":"104","street_number_addition":"C","latitude":52.3755598,"longitude":4.9028406}
curl --location --request GET 'https://zylalabs.com/api/5013/dutch+postal+code+tracker+api/6338/address+by+post+code+and+house+number?postal_code=1011AJ&house_number=104' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint you must indicate a postal code in the parameter.
{"house_numbers":[{"street":"Prins Hendrikkade","street_number":"106","street_number_addition":"A"},{"street":"Prins Hendrikkade","street_number":"107","street_number_addition":"3"},{"street":"Prins Hendrikkade","street_number":"106","street_number_addition":"B"},{"street":"Prins Hendrikkade","street_number":"107","street_number_addition":"2"},{"street":"Prins Hendrikkade","street_number":"104","street_number_addition":"C"},{"street":"Prins Hendrikkade","street_number":"105","street_number_addition":"1"},{"street":"Prins Hendrikkade","street_number":"105","street_number_addition":"H"},{"street":"Prins Hendrikkade","street_number":"104","street_number_addition":"B"},{"street":"Prins Hendrikkade","street_number":"106","street_number_addition":"C"},{"street":"Prins Hendrikkade","street_number":"107","street_number_addition":"H"},{"street":"Prins Hendrikkade","street_number":"106","street_number_addition":"D"},{"street":"Prins Hendrikkade","street_number":"107","street_number_addition":"1"},{"street":"Prins Hendrikkade","street_number":"104","street_number_addition":"D"},{"street":"Prins Hendrikkade","street_number":"104","street_number_addition":"A"},{"street":"Prins Hendrikkade","street_number":"105","street_number_addition":"2"}]}
curl --location --request GET 'https://zylalabs.com/api/5013/dutch+postal+code+tracker+api/6339/house+numbers+by+postal+code&postalcode=Required' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint you must indicate a post code in the parameter.
{"valid":true}
curl --location --request GET 'https://zylalabs.com/api/5013/dutch+postal+code+tracker+api/6340/post+code+validation&postcode=Required' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Users must enter a postal code or house number to obtain geodata.
The Dutch Postal Code API designed to provide users with access to accurate and up-to-date zip code data for the Netherlands.
There are different plans to suit all tastes, including a free trial for a small number of requests, but your rate is limited to avoid abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
The API returns full address details, including street, number, postal code, province, municipality, city, and precise geographic coordinates.
This endpoint returns detailed address information, including the province, municipality, city, postal code, street name, street number, street number addition, and geographic coordinates (latitude and longitude).
Users must provide a postal code as a parameter to retrieve a list of associated house numbers, including street names and any additional identifiers for each house number.
The response is structured as a JSON object containing a single field, "valid," which indicates whether the provided postal code is valid (true) or invalid (false).
This endpoint provides a list of house numbers associated with a specific postal code, including street names, street numbers, and any additional identifiers for each house number.
Key fields include "province," "municipality," "city," "postal_code," "street," "street_number," "street_number_addition," "latitude," and "longitude," which provide comprehensive address details.
The API utilizes official datasets to ensure that postal codes conform to established formats and standards, reducing input errors and enhancing data quality.
Common use cases include validating user-entered postal codes during online forms, ensuring accurate shipping addresses in e-commerce, and maintaining accurate customer records in CRM systems.
Users can integrate the returned address details into their applications for address verification, enhance user experience by auto-filling address fields, and improve logistics by optimizing delivery routes based on accurate postal code data.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
275ms
Service Level:
100%
Response Time:
155ms
Service Level:
100%
Response Time:
181ms
Service Level:
100%
Response Time:
1,026ms
Service Level:
100%
Response Time:
121ms
Service Level:
100%
Response Time:
195ms
Service Level:
100%
Response Time:
205ms
Service Level:
100%
Response Time:
5,227ms
Service Level:
100%
Response Time:
132ms
Service Level:
100%
Response Time:
233ms
Service Level:
100%
Response Time:
819ms
Service Level:
100%
Response Time:
1,541ms
Service Level:
100%
Response Time:
3,408ms
Service Level:
100%
Response Time:
28ms
Service Level:
100%
Response Time:
861ms
Service Level:
100%
Response Time:
638ms
Service Level:
100%
Response Time:
1,017ms
Service Level:
100%
Response Time:
427ms
Service Level:
100%
Response Time:
1,837ms
Service Level:
100%
Response Time:
0ms