Skip to content

Repairs & storage

Both resources are read-only and work with a READ key (Authentication & scopes). Repairs and storage are requested and managed in the Fleet Cockpit or with Fleet support.

A repair follows a device from the request to its return:

REQUEST_RECEIVED → AWAITING_PICKUP → PICKED_UP → REPAIR_IN_PROGRESS → IN_RETURN → COMPLETED

It can also be ON_HOLD while it waits on something, or CANCELLED. COMPLETED and CANCELLED repairs are closed.

  • GET /repairs lists repairs of your devices, newest first. Filter with device_id and status.
  • GET /repairs/:repair_id returns one repair.

Each repair includes the repairer, pickup and return tracking numbers, the request, pickup, return and closing dates, and loan_device_id when Fleet lent you a replacement device.

A storage stay covers one period during which a device is kept in a Fleet warehouse:

status Meaning
ACTIVE Stored at Fleet
ENDING On its way back to you
ENDED Delivered back
CANCELLED Never stored
  • GET /storage-stays lists stays of your devices, newest first. Filter with device_id and status.
  • GET /storage-stays/:storage_stay_id returns one stay.

Each stay includes the storage country_code, the intake quality grade and factory_reset flag, the start and end dates, and the ids of the inbound and outbound shipments (also listed in the device parcels). Storage requests that were never submitted are not returned.

Every device embeds its open repair (repair) and current stay (storage), and its location.type is AT_REPAIRER or FLEET_STORAGE while it is away. To list every stored device, call GET /devices?location_type=FLEET_STORAGE. See Devices.

  • API reference — Repairs and Storage stays tags for fields, filters and error codes (REPAIR_NOT_FOUND, STORAGE_STAY_NOT_FOUND).