The Netherlands Postal Code Search API is designed to provide users with accurate validation and comprehensive lookup data relating to Dutch zip codes. By prioritizing accuracy and reliability, this API enables users to improve address validation processes and optimize postal code queries for applications targeting the Netherlands.
Rely on the Netherlands Postal Code Search API to accurately validate Dutch zip codes entered into applications. Based on official data sets, the API performs thorough validation procedures, ensuring compliance with official formats and validity according to established standards. By reducing postal code entry errors, users can improve data integrity and user experience in their applications.
In addition to validation, the Netherlands Postal Code Search API extends the Dutch zip code query capabilities. Users gain access to detailed information linked to specific postal codes, including city, municipality, province and other relevant details. This facilitates accurate validation and enrichment of addresses within applications, ensuring users have access to accurate address details.
In summary, the Netherlands Postal Code Search API is a valuable resource for users looking to refine address validation processes and streamline zip code lookup functions for Netherlands-oriented applications. Equipped with accurate validation, extensive search capabilities, real-time data accessibility and seamless integration, the API enables users to maintain the accuracy and reliability of 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: 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/3838/netherlands+postal+code+search+api/4482/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/3838/netherlands+postal+code+search+api/4483/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":false}
curl --location --request GET 'https://zylalabs.com/api/3838/netherlands+postal+code+search+api/4484/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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
Users must enter a postal code or house number to obtain geodata.
The Netherlands Postal Code Search 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.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). 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 paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
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.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, look at the βX-Zyla-API-Calls-Monthly-Remainingβ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
154ms
Service Level:
100%
Response Time:
224ms
Service Level:
100%
Response Time:
243ms
Service Level:
100%
Response Time:
268ms
Service Level:
100%
Response Time:
244ms
Service Level:
100%
Response Time:
132ms
Service Level:
100%
Response Time:
112ms
Service Level:
100%
Response Time:
209ms
Service Level:
100%
Response Time:
917ms
Service Level:
100%
Response Time:
465ms
Service Level:
100%
Response Time:
202ms
Service Level:
100%
Response Time:
1,235ms
Service Level:
100%
Response Time:
742ms
Service Level:
100%
Response Time:
239ms
Service Level:
100%
Response Time:
685ms
Service Level:
100%
Response Time:
1,069ms
Service Level:
100%
Response Time:
492ms