Quickstart.

Get from a fresh account to a working API request in three steps. Full reference at docs.rijwind.com.

1

Get an API key

  1. Create an account — a default project and free plan are provisioned automatically.
  2. Open /dashboard/projects and pick your default project.
  3. Click New key. Save the rw_live_… string — it's shown once.
2

Make a request

Pass your key in the Authorization header. Same key works across every endpoint.

curl https://api.rijwind.com/v1/geocode/search \
  -H "Authorization: Bearer rw_live_••••" \
  -d 'q=Damrak 1, Amsterdam'
3

Understand quotas

Each plan ships with a monthly request budget that resets on the first of each calendar month.

  • Hard cap — returns HTTP 429 once the budget is empty.
  • Soft cap — logs the overage, never blocks, and you settle the difference on the next invoice.

See pricing for the current per-plan limits.

Available endpoints

v1 surface.

GET/v1/tiles-tokenShort-lived signed URL for the basemap PMTiles file.
GET/v1/geocode/searchForward geocoding — turn an address or place name into coordinates.
GET/v1/geocode/autocompleteType-ahead suggestions. Billed at 0.1 units per call.
GET/v1/geocode/reverseReverse geocoding — turn coordinates into the nearest address.
POST/v1/routeTurn-by-turn directions between waypoints. Profiles: auto, bicycle, pedestrian.
POST/v1/matrixTravel-time matrix between sources and targets. Capped at M × N ≤ 2500.
POST/v1/isochroneReachable-area polygons from a single origin. Capped at L × C ≤ 4.

Full reference is on docs.rijwind.com.

Per-endpoint schemas, error codes, parameter tables, and the OpenAPI spec for every endpoint.