getapi-nl Geolocation services API
The Geolocation services API from getapi-nl — 1 operation(s) for geolocation services.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/getapi-nl:getapi-nl-geolocation-services-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: GetApi Geolocation services API
version: 0.0.1
description: '## Authentication
All API endpoints require authentication. Include your API key in every request using **one** of the following methods:
**Option 1 — X-Api-Key header (recommended)**
```
X-Api-Key: ga_live_xxxxxxxxxxxxxxxxxxxx
```
**Option 2 — Bearer token**
```
Authorization: Bearer ga_live_xxxxxxxxxxxxxxxxxxxx
```
You can generate and manage API keys in your dashboard.
## AI & Agent Payments (x402)
Some endpoints support direct payments for AI agents via the **x402** protocol (https://www.x402.org).
No API key or account is needed. Send a normal request without key;
the server will respond with **HTTP 402** and a `PAYMENT-REQUIRED` header:
```
PAYMENT-REQUIRED:
```
This base64 string contains, among other things, `network`, `asset`, `amount`, and `payTo`.
Your agent signs an EIP-3009 *transferWithAuthorization* for the specified `amount` of USDC to that `payTo` address,
encodes the signature as base64, and resubmits the request with:
```
PAYMENT-SIGNATURE:
```
The server verifies the signature via a facilitator, provides the data, and settles the payment on-chain.
The success response includes a `PAYMENT-RESPONSE` header containing the transaction information.
A one-time `nonce` prevents replay attacks. Payments are made in USDC on **Base**;
the price is determined by the `credit_cost` of the endpoint.'
contact:
email: info@wdnoord.nl
x-guidance: 'GetAPI.nl is een Nederlandse API-platform voor lookups en validaties (postcode,
adres, kenteken, BTW, e-mail, KVK, IBAN, energiemaatwerk, overheidsdata). Elke
endpoint accepteert een API key via de X-Api-Key header of Authorization:
Bearer <key>.
Sommige endpoints zijn ook direct betaalbaar voor AI-agents via het x402-protocol
(https://www.x402.org) zonder account of API key: stuur een verzoek zonder key,
de server antwoordt met HTTP 402 en een PAYMENT-REQUIRED header (base64 JSON met
network, asset, amount, payTo). Teken daarna een EIP-3009 transferWithAuthorization
voor het gevraagde bedrag in USDC op Base en hertrail met een PAYMENT-SIGNATURE
header. De server verifieert, levert de data en settleert on-chain.
Tips voor agents:
- Lees eerst de PAYMENT-REQUIRED header van een 402-antwoord; die is leidend.
- Geef altijd de exact door de server gevraagde parameters mee.
- Een endpoint met een "x-payment-info" blok vereist betaling voor gebruik.'
servers:
- url: https://api.getapi.nl
description: GetAPI
security:
- ApiKeyAuth: []
- BearerAuth: []
tags:
- name: Geolocation services
paths:
/v1/lookup/postcode:
get:
operationId: lookup.postcode
description: 'Returns address data for a Dutch postcode, optionally refined by house number.
There are multiple sources available with varying coverage and accuracy.'
summary: Zipcode lookup for the Netherlands
tags:
- Geolocation services
parameters:
- name: postcode
in: query
required: true
schema:
type: string
pattern: ^[1-9][0-9]{3}\s?[A-Za-z]{2}$
- name: number
in: query
schema:
type:
- integer
- 'null'
minimum: 1
maximum: 99999
responses:
'200':
description: Postcode found
content:
application/json:
schema:
type: object
examples:
- found: true
postcode: 1011AB
street: De Ruijterkade
city: Amsterdam
municipality: Amsterdam
number: null
lat: 52.37779461
lon: 4.90564828
properties:
found:
type: boolean
postcode:
type: string
street:
type:
- string
- 'null'
city:
type:
- string
- 'null'
municipality:
type:
- string
- 'null'
number:
type:
- integer
- 'null'
lat:
type:
- number
- 'null'
lon:
type:
- number
- 'null'
required:
- found
- postcode
- street
- city
- municipality
- number
- lat
- lon
'422':
$ref: '#/components/responses/ValidationException'
'404':
description: Not found
content:
application/json:
schema:
type: object
examples:
- found: false
postcode: 9999ZZ
street: null
city: null
municipality: null
number: null
lat: null
lon: null
error: not_found
message: Niet gevonden.
properties:
found:
type: boolean
postcode:
type: string
street:
type: 'null'
city:
type: 'null'
municipality:
type: 'null'
number:
type: 'null'
lat:
type: 'null'
lon:
type: 'null'
error:
type: string
message:
type: string
required:
- found
- postcode
- street
- city
- municipality
- number
- lat
- lon
- error
- message
'402':
description: Payment Required
x-payment-info:
price:
mode: fixed
currency: USD
amount: '0.005000'
protocols:
- x402: {}
components:
responses:
ValidationException:
description: Unprocessable content
content:
application/json:
schema:
type: object
properties:
error:
type: string
description: Machine-readable error code.
message:
type: string
description: Human-readable error message.
errors:
type: object
description: A detailed description of each field that failed validation.
additionalProperties:
type: array
items:
type: string
required:
- error
- message
- errors
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: X-Api-Key
BearerAuth:
type: http
scheme: bearer