Unavailabilities define a specific time range during which a TransportResource is unavailable. This can be due to, for example, technical issues. During its duration, the TransportResource can not be matched with an available Employee and used as part of the planning.
This endpoint allows you to create an Unavailability with a generated ID. This can be used for ad hoc Unavailabilities or situations where the source system does not contain any unique IDs.
See the PUT operation for more information on the functional impact of adding a new unavailability.
The RFC7240 Prefer header indicates that a particular server behavior is preferred by the client but is not required for successful completion of the request (see RFC 7240).
The following behavior (see Examples) is supported by this API:
- return=<minimal|representation> is used to suggest the server to return using 204 without resource (minimal) or using 200 or 201 with resource (representation) in the response body on success.
- Mock serverhttps://developer.conundra.eu/_mock/apis/resource-management/resources-api/transport-resource/{id}/unavailability
- Resources API Productionhttps://api.conundra.eu/resource-management/v1/transport-resource/{id}/unavailability
{ "from": "2021-01-01T06:00:00Z", "to": "2021-01-10T06:00:00Z", "description": "maintenance" }