omgevingsloketinzage.omgeving.vlaanderen.be APIomgevingsloketinzage.omgeving.vlaanderen.be ↗
Search and retrieve Flemish environmental permits (omgevingsvergunningen) by location or keyword. Access permit details, procedure phases, and building actions.
curl -X GET 'https://api.parse.bot/scraper/2e31d0cd-fe7c-4be1-89b0-c4850c4edf3e/search_permits?page=0&size=20&query=Gent' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for environmental permits by municipality, project name, or address. Returns paginated results sorted by project name.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (0-based) |
| size | integer | Results per page |
| queryrequired | string | Municipality name or project keyword (e.g. 'Gent', 'Antwerpen') |
{
"type": "object",
"fields": {
"last": "boolean, whether this is the last page",
"first": "boolean, whether this is the first page",
"content": "array of permit summaries, each with uuid, puuid, and projectNaam",
"pageable": "object with pagination metadata including pageNumber, pageSize, sort, offset",
"numberOfElements": "integer, count of results on this page"
},
"sample": {
"data": {
"last": false,
"size": 20,
"empty": false,
"first": true,
"number": 0,
"content": [
{
"uuid": "8uWN7Hn1Th6xIoDH8uYjbg",
"puuid": "H0nCtBT3Sl-mBrBUXVzCgw",
"projectNaam": "080.Friedrich Froebelstraat.Gent, (2026025273)"
}
],
"pageable": {
"sort": [
{
"property": "p.naam",
"direction": "ASC"
}
],
"offset": 0,
"pageSize": 20,
"pageNumber": 0
},
"numberOfElements": 20
},
"status": "success"
}
}About the omgevingsloketinzage.omgeving.vlaanderen.be API
This API exposes 2 endpoints for accessing environmental permits from the Flemish government's omgevingsloketinzage portal. Use search_permits to find permits by municipality or keyword — returning paginated summaries with UUIDs and project names — then call get_permit_details to retrieve the full permit record including procedure phases, administrative decisions, appeal deadlines, and building action specifics.
Searching Permits
The search_permits endpoint accepts a query parameter — a municipality name like Gent or Antwerpen, a street name, or a project keyword — and returns paginated results. Each item in the content array includes a uuid, a puuid, and a projectNaam. Pagination is controlled via page (0-based) and size, and the response includes a pageable object with pageNumber, pageSize, offset, and sort metadata, plus boolean first and last flags to detect page boundaries.
Permit Details
The get_permit_details endpoint accepts either the uuid from search results or an OMV project_number (e.g. 2026025273). The response bundles four distinct data objects: overview contains core permit metadata including projectnummer, bevoegdeOverheid (competent authority), beslissing (decision), and eindDatumBeroep (appeal deadline); procedure is an array of procedure phase objects with subOnderdelen sub-steps; project_info holds general project information; and building_actions returns a paginated list with totalElements and a content array describing specific building or location actions tied to the permit.
Coverage Scope
All data is scoped to Flanders (Belgium). Permits are identified by OMV reference numbers, which follow Flemish administrative numbering conventions. The bevoegdeOverheid field identifies which governmental body holds authority over each permit — useful when filtering for municipal versus provincial or regional decisions.
- Monitor permit activity in a specific municipality by querying
search_permitswith a municipality name and tracking newprojectNaamentries - Build a permit-status dashboard showing
beslissingandeindDatumBeroepfrom theoverviewobject for ongoing construction projects - Audit procedure compliance by inspecting the
procedurearray and itssubOnderdelenphases for a given permit UUID - Identify which competent authority (
bevoegdeOverheid) issued a permit to determine municipal vs. regional jurisdiction - Enumerate building actions tied to a parcel by iterating through
building_actions.contentfor permits matching an address query - Cross-reference an OMV project number from a physical notice board by passing it directly as
project_numbertoget_permit_details
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does omgevingsloketinzage.omgeving.vlaanderen.be have an official developer API?+
What does `get_permit_details` return beyond the overview?+
overview (project number, competent authority, decision, appeal end date), procedure (array of phase objects each with subOnderdelen sub-steps), project_info (general project metadata), and building_actions (paginated list of building/location actions with totalElements and a content array). Providing either a uuid or a project_number is sufficient to retrieve all four.Can I filter search results by permit status or decision type?+
search_permits filters by the query string (municipality name or keyword) and supports pagination via page and size. Filtering by beslissing (decision) or permit status is not exposed as a parameter. You can fork this API on Parse and revise it to add a status-filter endpoint if your use case requires it.Does the API cover permits from Brussels or Wallonia?+
Are document attachments or permit PDF files accessible through this API?+
inhouden array in get_permit_details provides content version references, but PDF or document retrieval is not covered. You can fork this API on Parse and revise it to add document-fetch endpoints if attachment access is needed.