API Migration Guides

Migration Guide 1.x to 2.x

These endpoints and properties are officially deprecated and will be retired on Saturday, 28 February 2026.
Grab your migration tools, duct tape, and maybe a soothing playlist. Let's do this.

Removed Endpoints

PATCH /api/v1/request-for-groundworks/{gipodId}:

See release note July 2025
Replaced with /api/v2/request-for-groundworks/{gipodId}
- ‘ReasonTypeId' is required for status ‘Ingetrokken door aanvrager’ & ‘Ingetrokken door domeinbeheerder’.
- Renamed field ‘ReasonStatus’ to ‘Reason’

GET /api/v1/mobility-hindrances/geojson:

See release note March 2025
Replaced with /api/v1/mobility-hindrances/zones/geojson for mobilityhindrance zones
Replaced with /api/v1/mobility-hindrances/diversions/geojson for diversions

GET /api/v1/resources:

Deprecated since August 2021
Replaced with /api/v1/entities

Changed Endpoints

GET /api/v1/trench-synergies/{gipodId}:

See release note July 2025 & June 2020
ContactOrganisations removed, use ContactOrganisation (singular, consistent)
Zone removed, use Geometry (conform OSLO)

GET/api/v1/events/{gipodId}/zones/{zoneId}:

See release note June 2020
Zone removed, use Geometry (conform OSLO)

GET/api/v1/groundworks/{gipodId}/zones/{zoneId}:

See release note June 2020
Zone removed, use Geometry (conform OSLO)

GET/api/v1/works/{gipodId}/zones/{zoneId}:

See release note June 2020
Zone removed, use Geometry (conform OSLO)

GET/api/v1/mobility-hindrances/{gipodId}/zones/{zoneId}:

See release note June 2020
Zone removed, use Geometry (conform OSLO)