Delete mobility hindrance

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/DeleteMobilityHindrance

Delete a given mobility hindrance.

Mobility hindrance with linked signaling permits are not possible to delete.

Register mobility hindrance

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/RegisterMobilityHindrance

A new property “statusId” is added to the request.

The following statuses can be used:

• In Opmaak: /api/v1/taxonomies/statuses/0a4ee99b-8b8a-47c8-913f-117220febee0

• Gevalideerd: /api/v1/taxonomies/statuses/5cc9ee5b-fa97-4d71-8851-51a9d0e2ebd0

Status “Gevalideerd“ can only be set by a local government.

Get mobility hindrance

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/GetMobilityHindrance

A new property “status“ is added to the response.

Modify mobility hindrance

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/ModifyMobilityHindrance

Possible to modify the status of a given mobility hindrance. Only a local government can modify the status.

To modify the status of an extra patch key “StatusId“ is available.

The following statuses can be used:

• In Opmaak: /api/v1/taxonomies/statuses/0a4ee99b-8b8a-47c8-913f-117220febee0

• Gevalideerd: /api/v1/taxonomies/statuses/5cc9ee5b-fa97-4d71-8851-51a9d0e2ebd0

Search notifications

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/GetNotifications

All notification data is added in each member of the response.

• value

• category

• organisation

• data

• createdOn

• expiresOn

• status

Get notification types

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/GetNotificationTypes

In the response all notifications types were returned in flat list. A hierarchy is added in the structure of notification types.

• All notification types related to “trench synergies” can be found under: api/v1/taxonomies/notificationtypes/9fa45055-1034-4cc5-9e90-854538843a9c

• All notification types related to “trench synergy requests” can be found under: api/v1/taxonomies/notificationtypes/9408cee4-df86-4869-abbe-e71f7cb6b99

Get organisation detail

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/GetOrganisation

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/GetCurrentlyLoggedOnOrganisation

• The externalIdentifiers property now contains the niscode when the organisation is a local gove-ornment.

• GeoSecureId removed from external identiefiers.

Search trench synergy requests

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/SearchTrenchSynergyRequests

Extra query string parameters are added:

• groundworkid: search trench synergy requests where the given groundworks are added in an answer.

• answeringorganisationid: search trench synergy requests answered by the given organisation.

• answer: search for trench synergy request with a postive or negative answer.

https://github.com/Informatievlaanderen/GIPOD/issues/102

Modify trench synergy

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/ModifyTrenchSynergy

• Possible to modify status of a trench synergy to status “Niet uitgevoerd“: /api/v1/taxonomies/statuses/34df34f3-db29-4dc7-ae10-01523c232652

Modify groundwork

Modify work

Modify event

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/ModifyGroundwork

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/ModifyWork

https://private-api.gipod.beta-vlaanderen.be/api-documentation.html#operation/ModifyEvent

Possible to modify the owner of a groundwork, work, event to another organisation within the organisation hierarchy of the current owner.

It’s possible to modify to modify the owner by adding the patch-key “OwnerId“ in the request.