Service · Software development

Build a PostcodeAPI integration.

Address autocomplete in your web form, validation in your ERP or CRM, geocoding for your route planning. We integrate PostcodeAPI.nu, the PostNL Postcode API, Postcode.nl or BAG-direct into your application, including caching, a fallback flow and an optional offline mode.

PostcodeAPI.nuPostNL APIBAG integrationOffline mode

A postcode API is a commodity. The integration isn't.

Most Dutch postcode APIs deliver perfectly good data. The difference between a pleasant address input and an irritating form lies not in the provider but in how you integrate it: debouncing, caching, error handling, fallback behaviour when the API is briefly down, and what it looks like for the end user on a train with a flaky connection. The same provider can feel smooth in one application and irritating in another. The difference lies in the implementation choices around it.

We integrate postcode and address APIs into custom software, webshops, B2B portals and mobile apps. For some clients this runs purely in the cloud; for others, such as field service apps or legacy ERP, we build a hybrid with a local BAG dataset so that it also works without internet. Sometimes no external API at all is the right choice and we integrate directly with the Basisregistratie Adressen en Gebouwen (Dutch national address and building register). Which approach fits depends on your volume, sensitivity to latency, whether you process international addresses, and how important the UX is at the point of entry.

For broader integration questions, we fit the integration into the context of your wider API landscape: how the postcode layer relates to your CRM, order system, carrier integrations and any payment providers. A standalone address component that doesn't evolve with the rest of your stack only creates maintenance overhead in the long run.

Three flavours of address integration.

Which one fits depends on where the address entry happens, how much volume you handle, and whether it also needs to work offline. In the first conversation we advise which approach suits your situation.

Compact project · fixed sprint budget

Address autocomplete in a web form

The customer types a postcode and house number, and the street and town appear automatically. A common approach for webshop checkouts, lead forms and application flows. PostcodeAPI.nu or Postcode.nl as the source, with debounce and caching built in, and clear error messages if the API doesn't respond. We connect the component to your existing form, whether React, Vue, Astro, Livewire or an older framework, without turning your front end upside down. Validation runs both client-side for quick feedback and server-side for security, and it stores normalised addresses in a fixed format that downstream systems can process.

PostcodeAPI.nuDebounceCachingForm validation
Mid-sized project · fixed sprint budget

Address validation in ERP, CRM or back office

Cleaning up existing address data, validating new records on entry, and detecting duplicate customers based on a normalised address. This includes batch validation of your existing database and a schedule for synchronisation when address changes occur in the BAG (the Dutch national address register). For larger customer databases, we start with a data-quality report: how many records are incomplete, how many house number additions are missing, and which addresses no longer match the BAG because a street name has changed. Based on that, we decide which records can be corrected automatically and which need manual attention. The integration works with Exact, AFAS, Twinfield, Microsoft Dynamics, Salesforce, HubSpot and most custom back-ends.

Batch validationBAG syncNormalisationDuplicate detection
Larger project · fixed sprint budget

Hybrid with an offline mode for field service

For inspectors, engineers and delivery drivers who also work in places without coverage. We build a local dataset (a BAG export or subset) that syncs periodically, plus a fallback to the online API as soon as a connection is available again. On top of that comes geocoding for route planning and international coverage via Google or Loqate. The local dataset only contains the regions where your people actually work, which saves a great deal of storage and sync time. Updates run via FME or an automated feed from PDOK, conflict resolution is predictable (source data wins, with an audit log for manual overrides), and the app knows for itself when an area needs to be resynchronised.

Offline datasetBAG exportGeocodingInternational

What you get at the end.

A working postcode or address integration in your application, plus everything you need to manage it yourself and keep costs under control.

We don't deliver a black-box component with an API key inside, but code your team understands and can adapt. That includes tests, monitoring hooks and clear documentation of the choices we made: at what volume a caching upgrade becomes worthwhile, when a second provider makes sense, and how you can expand or shrink the offline dataset yourself.

  • The integration in your applicationAPI client, autocomplete component (web or mobile), validation layer in the back-end and an integration with your ERP or CRM.
  • Caching layerRedis or an in-memory cache with a TTL, so you don't pay for an API call on every keystroke. For high-volume customers this makes a substantial difference.
  • Fallback flowIf the chosen provider is down, the application falls back gracefully to manual entry or a second source. The end user won't notice a thing.
  • Optional offline datasetFor applications that also need to work without internet: a local BAG subset with a sync mechanism. Updates arrive periodically via FME or a feed.
  • DocumentationHow the integration works, how to rotate API keys, what to do when rate-limit errors occur, and how to add a second provider yourself.
  • Management contract (optional)Monitoring of the provider's uptime, alerts when rate limits are exceeded, and ongoing upkeep when APIs get new versions.

When a postcode integration makes sense.

Four signals that bring clients to us. If you recognise one of them, we'd be glad to talk further.

Webshop & conversion

Too many address errors in orders

Customers mistype, forget house number additions, or abandon the checkout halfway because the form feels tedious. Autocomplete often halves the number of wrong deliveries, noticeably shortens the checkout and ensures your carrier integration receives correctly formatted addresses. For B2B checkouts, a KvK (Dutch Chamber of Commerce) lookup is often combined with the address validation, so business customers are done with a single field.

Field service & offline

No coverage on site

Your engineers, inspectors or delivery drivers regularly work in places where mobile internet drops out: remote industrial estates, underground car parks, agricultural areas. A hybrid approach with an offline dataset and a sync mechanism keeps data entry reliable, even without a connection. As soon as coverage returns, changes sync back to the central database automatically, without the user having to do anything manually.

Costs and volume

API costs are rising

You've grown, and the monthly postcode bill is higher than expected. A good caching layer, debouncing and, if needed, your own BAG export bring the costs back down without users noticing anything. For some clients it also means a single shared postcode layer for several applications, instead of a separate bill with the same provider for each app.

Compliance and data quality

BAG compliance required

For property systems, municipalities and housing associations, a direct integration with the Basisregistratie Adressen en Gebouwen (BAG, the Dutch national register of addresses and buildings) is often mandatory or strongly preferred. Address data must match the official register exactly, changes must be traceable and historical address versions must be retrievable. Insurers and mortgage providers face similar data-quality pressure: a wrong house number in a policy contract is expensive to correct afterwards.

How an integration project works.

1

Introduction & scope

We discuss where address entry takes place, what volume you expect, whether international addresses are involved and whether offline working is a requirement. We also look at which downstream systems need to receive the normalised address, which privacy requirements apply and how your current checkout or data-entry flow performs. Based on that, we advise which provider and which architecture fit.

2

Provider selection and PoC

We test one or two providers (PostcodeAPI.nu, PostNL, Postcode.nl or BAG direct) against your use case. A short proof of concept shows how the UX feels and what the response times are on your real data. In borderline cases we run the PoC with two sources in parallel, so you can experience the difference yourself before committing to a provider and its cost structure.

3

Building in sprints

A working build every two weeks. First the happy path, then rate limiting, caching, fallback and, if needed, offline mode. You test along with us, and we incorporate your feedback in the next sprint. At the end of each sprint you get a short demo plus an honest status update on risks and open points, with no surprises at the end.

4

Rollout & support

A phased rollout (first a small share of traffic, then scaling up) and ongoing monitoring to check that the chosen provider keeps delivering. For rate-limit or availability incidents, we respond according to the agreed level. Afterwards you can choose to manage it yourself, with a handover and runbook, or ongoing management in which we take care of provider upgrades, rate-limit adjustments and new BAG versions.

Frequently asked questions.

The questions clients ask before we start, drawn from our conversations as well as from search results.

Which postcode API should I choose: PostcodeAPI.nu, PostNL or something else?
For most SME applications, PostcodeAPI.nu is a good starting point: simple onboarding, a free tier for low volumes and a clean REST API. Postcode.nl is more commercially oriented and has a more extensive dataset (including ownership information and historical address versions), which is interesting if you need more than just address autocomplete. The PostNL Postcode API is PostNL's official offering, handy if you already ship with PostNL and want to match address data with how PostNL uses it itself. For enterprise volumes, or when you need direct BAG compliance, we would rather integrate directly with the Basisregistratie Adressen en Gebouwen via PDOK. We advise per project, as it depends heavily on volume, use case and the other systems the data needs to go to.
Can a postcode API also be used offline?
Yes. For applications where working offline matters, such as field-service apps, inspections or deliveries in rural areas, we build a hybrid. A local subset of the BAG (the Dutch official address registry) is downloaded to the device periodically. While there is a connection, the app uses the online API; if it drops, the app quietly switches to the local dataset. We determine the sync frequency and the size of the subset based on your working area and device storage. For a fleet of tablets across the Netherlands, a full-NL BAG subset is perfectly workable; for mobile-first apps with storage constraints, we split it up by region. When the device is back online, changes (newly created addresses, location adjustments) are automatically sent back to the server, with a clean audit trail of what was entered when, in which offline session.
What determines whether a postcode API becomes expensive?
Mainly the number of API calls. Many teams send a lookup call on every keystroke, which adds up quickly for a busy web shop. With debouncing (waiting until the user pauses typing), caching at postcode level and a second layer at house-number level, we can often cut the number of calls substantially. Another frequently overlooked factor is bot and crawler traffic that hits lookup endpoints without ever resulting in an order. For that, we set up per-IP rate limiting and CAPTCHA fallbacks on heavily used endpoints. At very high volumes, your own BAG export becomes interesting: it requires an upfront investment, but after that there are no variable costs and you are not tied to a single provider's pricing.
How do we handle international addresses?
Dutch postcode APIs only cover the Netherlands. For cross-border customers, such as international web shops, logistics and SaaS, we combine a Dutch provider for Dutch addresses with the Google Address Validation API or Loqate for the rest of the world. We make that choice based on the countries that actually appear in your order flow and on privacy considerations (Loqate is a European supplier, while Google processes data in its own data centres). Address normalisation ensures the end result in your database always has the same fields, regardless of the source. That makes a big difference for downstream integrations with carriers, invoicing software and your CRM.
What is the difference between using the BAG directly and using a postcode provider?
The BAG (Basisregistratie Adressen en Gebouwen, the Dutch register of addresses and buildings) is the official Dutch registry, managed by the Kadaster and available via PDOK. Postcode providers also use BAG data as their basis, but put a user-friendly API on top with fast autocomplete endpoints and a commercial SLA. For most applications, a provider is quicker and simpler to integrate. Connecting directly to the BAG via PDOK is worthwhile where there are compliance requirements (real estate, municipalities, housing associations), at very high volumes where provider costs become significant, or if you already use other PDOK data, such as parcels, buildings or WOZ (property valuation) data, and it makes sense to draw from the same source.
What if the chosen API goes down or hits its rate limit?
We build for that structurally. A retry mechanism with exponential backoff absorbs short hiccups. In the event of a longer outage, the application falls back to manual entry or a second provider. For mission-critical applications, we often opt for two providers in parallel (the first hits its rate limit, the second takes over) or a hybrid with a local fallback. We actively monitor response times and error rates so you see a problem before your users notice it. Alerts go through your existing channel, whether that is Slack, Teams or your own monitoring platform.
Do you work with our in-house IT team?
Almost always. We deliver not only working code, but also documentation, an incident runbook and knowledge transfer in the final sprint. Your team can then maintain the integration itself, or we can do it under an ongoing support contract. Often it's a mix: you manage it day to day, and we're available for extensions, provider changes and BAG version upgrades. The code lives in your own repository, following the same standards (linting, tests, CI) as the rest of your codebase — no vendor lock-in and no separate stack to learn.

Talk to us about your postcode integration.

A half-hour introductory call, with no obligation. We listen to your use case, ask about volumes and offline requirements, and advise on which provider and architecture fit. If it's a match, we'll scope a first sprint. If not, we'll say so honestly. For broader integration questions, we also look at your ERP environment and web applications.

Edit content