Stadiq API

Official GIPOD road works and De Lijn detours for any point in Flanders, as JSON, plus a dated archive of what changed around Antwerp. Free key, no card.

Contents

Get a key

Enter your email. We send a sign-in link that works once and expires after 15 minutes. It signs you in on the free developer plan and returns you to this page, where you create your key. You see it once, right after you create it: copy it then. We never email the key itself.

Free developer tier. No card, no dashboard account.

Or from a terminal
curl -X POST https://stadiq.app/api/v1/signup \
  -H "Content-Type: application/json" \
  -d '{"email":"you@company.be"}'

Already have a Stadiq account? Sign in with the same email and manage your keys in the app.

Make your first call

Send the key as a Bearer token. -i prints the headers, so you can see the quota next to the body.

Request
curl -i -H "Authorization: Bearer sq_live_…" \
  "https://stadiq.app/api/v1/disruptions?lat=51.2194&lng=4.4025"
Response for Groenplaats on 10 November 2026, abridged (33 lines)
HTTP/2 200
x-ratelimit-limit: 100
x-ratelimit-remaining: 99

{
  "radiusKm": 2,
  "unavailableFeeds": ["Open-Meteo", "KMI"],
  "partialFeeds": [],
  "summary": { "activeWorks": 2, "plannedWorks": 18, "transitDisruptions": 3, … },
  "construction": [
    {
      "id": "13468134",
      "description": "Ambulante handel Groenplaats 2",
      "status": "Lopende",
      "distanceKm": 0.05,
      "startDate": "2026-11-10T07:00:00Z",
      "endDate": "2027-05-12T18:00:00Z",
      …
    },
    …
  ],
  "transit": [
    {
      "id": "o-vt35ldq1e70o",
      "title": "Werkzaamheden Reetsesteenweg ( fase 1 en 3 )",
      "lines": ["180", "181", "508", "182"],
      "severity": "medium",
      "endDate": "2026-11-13T23:59:59",
      …
    }
  ],
  "retrievedAt": "2026-11-10T18:39:58.235Z"
}

Treat the key like a password: keep it in an environment variable or a local config file, never in a shared repository or a screenshot. If it leaks, revoke it in the dashboard (account menu, API en sleutels) and create a new one; the old key stops working at once.

A working key returns 200 with X-RateLimit-Limit and X-RateLimit-Remaining. A 401 means a missing or wrong key; 422 means the point is outside Flanders. Every endpoint, field and error code is in the API reference; the OpenAPI 3.1 spec is at /openapi.json.

GIPOD history and the Apify actor

The GIPOD feature service answers with what is registered now. We have read it daily since 11 April 2026, for Antwerp and 15 km around it, and GET /history returns what that archive holds within up to 1000 m of a point or address: each work and street occupation, when we first and last saw it, its published start, end and status, and every change to those three between captures.

Changes since 1 September 2026, 500 m around a point near the Desguinlei
curl -G https://stadiq.app/api/v1/history \
  -H "Authorization: Bearer sq_live_…" \
  -d lat=51.1931 -d lng=4.4033 \
  -d radius_m=500 -d since=2026-09-01

Newest day in the archive: 17 November 2026. The archive reads GIPOD once a day.

Real example: planned end dates that moved

The five most recent changes of a published end date in our archive of GIPOD. GET /history returns this per work, with the day we saw each change. A moved end date is a change in what GIPOD published. It is not a verified overrun.

Source: GIPOD, Digitaal Vlaanderen, Modellicentie Gratis Hergebruik Vlaanderen v1.0. Only works in the archive of Antwerp and 15 km around it.
GIPOD idWorkSeen onPlanned end beforePlanned end after
13468134Ambulante handel Groenplaats 22026-11-172027-05-172027-05-18
13468109Ambulante handel Groenplaats 12026-11-172027-05-172027-05-18
13472986Ambulante handel Lombardevest2026-11-172027-05-162027-05-18
13527824Ambulante handel Wilde Zee2026-11-172027-05-182027-05-19
13473343Ambulante handel Theodoor Van Rijswijckplaats (thv Nationalestraat)2026-11-172027-05-162027-05-18

Read coverage before works. It lists the days the archive missed, the days GIPOD returned a truncated result, and whether a live GIPOD read for the same point answered. If no day of your window was captured, coverage.state is unavailable and the empty list means unknown. GIPOD is published by Digitaal Vlaanderen under the Modellicentie Gratis Hergebruik Vlaanderen v1.0; every response carries the attribution text, which you show wherever you republish the data. Fields and errors are in the API reference.

On Apify

Without a Stadiq account, the same query runs as an Apify actor: give it an address or coordinates and a start date, and it returns one dataset row per work. It is paid per result on Apify, separate from the plans below. Open it in the Apify Store

What you get beyond the raw feed

GIPOD itself is free and official, and for a single lookup it is enough. What the API adds, and how to check each claim:

  • The source is named. Road works and street occupations are GIPOD, published by Digitaal Vlaanderen. A successful /history response carries the licence attribution in source.
  • Every answer is dated. /disruptions returns retrievedAt. /history returns coverage with the first archive day and every day that was missed. A source that is down is listed in unavailableFeeds, never shown as an empty result.
  • You see what changed. For Antwerp and 15 km around it, from 11 April 2026, the archive records the start, end and status changes it sees between its daily reads, per work. That is not the full history of GIPOD: it starts on that date, and days before 9 November 2026 hold only a slice of the works, which coverage reports.
  • Email alerts, no polling. A free account can opt in to a daily email when a new work is registered, or a date moves, within the coming week near a saved address. We do not offer outbound webhooks yet.
  • A contract you can read. The OpenAPI 3.1 spec and the RFC 9727 API catalog are public, the paths are versioned under /api/v1, and the spec carries its own version number.
  • Wrong data has a route. We republish GIPOD as published. If a record looks wrong, mail us the GIPOD id and we compare it with the register.

There is no uptime SLA and no status page yet. If you need either, tell us before you build on it.

Pricing

Two plans, priced per account and not per key. Start free, then upgrade for production volume and the GIPOD history. One flat monthly price, no usage tiers. There is no minimum term: after you cancel, the paid period runs to its end and is not renewed, and remaining days are not refunded unless the law says otherwise. See the terms.

Quotas reset at 00:00 UTC. The CLI and MCP server use the same key and quota.
PlanPriceCalls per dayFor
DeveloperFree, no card100Build and evaluate. No history endpoint.
API€29 per month incl. VAT10,000Production volume, including GIPOD history with revisions.

Get a free key

Subscribers cancel themselves in the app, in the “API en sleutels” dialog; the plan stays active to the end of the paid period. For a contract or a longer history: mail team@stadiq.app.

CLI and MCP server

Guides to the public sources

The registers behind Stadiq are public, and two need no key at all. If you only want road works, you do not need Stadiq:

Road works around Groenplaats, straight from GIPOD, no key
curl -s "https://geo.api.vlaanderen.be/GIPOD/ogc/features/v1\
/collections/INNAME/items\
?f=application/geo%2Bjson&limit=3\
&bbox=4.38,51.21,4.42,51.23"

Stadiq joins works and transit on one timeline for one address, filtering out results that cannot reach it. The guides document each source as it actually behaves.

Toon nog 1