The Dutch Postal Code API designed to provide users with accurate validation and detailed lookup information for Dutch postal codes. Focused on accuracy and reliability, this API provides developers with the means to improve address validation processes and streamline postal code lookup functions for applications targeting the Netherlands.
Users can rely on the Dutch Postal Code API to ensure the accuracy of Dutch postal codes entered into their applications. Leveraging official datasets, the API performs extensive validation checks to confirm that postal codes conform to the official format and are valid according to established standards. By reducing zip code entry errors, users can improve data quality and user experience in their applications.
In addition to validation, the Dutch Postal Code API provides extensive Dutch zip code query functions. Developers can retrieve detailed information associated with specific postal codes, including city, municipality, province and other relevant details. This enables accurate validation and enrichment of addresses within applications, ensuring that users have access to accurate address information.
In conclusion, the Dutch Postal Code API is a valuable tool for users who want to improve address validation processes and streamline zip code lookup functions for applications targeting the Netherlands. Thanks to its accurate validation, comprehensive search functions, real-time data access and ease of integration. The API enables users to ensure accurate and reliable postal code data in their applications.
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: 50 requests per second.
To use this endpoint you must indicate a postcode and a house number in the parameters.
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/3646/dutch+postal+code+api/4106/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/3646/dutch+postal+code+api/4107/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/3646/dutch+postal+code+api/4108/post+code+validation&postcode=Required' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Dutch Postal Code API REST API, simply include your bearer token in the Authorization header.
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
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.
Sure, you can use it and pay only when you use it. The credit canβt be expired.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected β plus overage fees applied when a developer exceeds a planβs quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
183ms
Service Level:
100%
Response Time:
1,549ms
Service Level:
100%
Response Time:
202ms
Service Level:
100%
Response Time:
239ms
Service Level:
100%
Response Time:
742ms
Service Level:
100%
Response Time:
589ms
Service Level:
100%
Response Time:
917ms
Service Level:
100%
Response Time:
555ms
Service Level:
100%
Response Time:
685ms
Service Level:
100%
Response Time:
117ms
Service Level:
100%
Response Time:
412ms
Service Level:
100%
Response Time:
226ms
Service Level:
100%
Response Time:
133ms
Service Level:
100%
Response Time:
1,060ms
Service Level:
100%
Response Time:
703ms
Service Level:
100%
Response Time:
1,097ms
Service Level:
100%
Response Time:
773ms