Skip to main content
Periods where a vehicle was unavailable. Delivered daily. Update key: external_system_id — one identifier per period, reused to close it

Columns

reason values

PLANNED_MAINTENANCE · UNPLANNED_REPAIR · ACCIDENT · MODIFICATION · OTHER

Closing a period

Closing works like a dismount: re-send the same external_system_id with in_service_at filled in and a newer last_updated. Do not send a separate row.
Re-sending a closed period with in_service_at empty and a newer last_updated re-opens it, setting the return-to-service time back to nothing. Once a period is closed, your exporter must keep carrying that value.
in_service_at must be strictly later than out_of_service_at — identical timestamps are rejected, so a period that opened and closed at the same recorded instant needs its timestamps separated before delivery.

Example

The first row is a closed period, the second still open:

Why a file gets rejected

Required fields, the enum and the ordering rule are reported together:
Vehicle resolution is checked afterwards, so these appear on a later attempt: