Get Driver Tag History
GET/drivers/tags/:identification_tag_id/history
This endpoint lists every assignment of one driver ID tag, past, running, future and lost, newest
first. Use it to see who held a tag and when. GET /drivers/tags only returns the current assignment.
Each item carries a status. ACTIVE means the assignment has started and not ended. SCHEDULED
means it starts in the future. ENDED means its end has passed. LOST means the tag was marked lost
on this assignment, whatever its dates. lost is true only for LOST items. unassigned_ts is
null when the assignment has no end.
Items are ordered by assigned_ts descending, then unassigned_ts descending. A tag with no
assignment returns 200 with an empty data array. A tag that does not exist, is deleted, or belongs
to another account returns 404.
A subuser receives only the assignments of drivers it can view, which is the same driver rule as
GET /drivers/tags, and meta counts only the returned ones. A tag that has assignments only of
drivers the subuser cannot view returns 200 with an empty data array.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 500
- 503
Successful operation
Unauthorized access. Authentication is required.
Access is forbidden. The user does not have permission to access this resource, or the account is not currently active.
The requested resource was not found.
Validation failed for the input parameters.
Internal server error.
Service temporarily unavailable. The request did not complete and can be retried after the number of seconds in the Retry-After header, when one is sent.
Response Headers
Seconds to wait before retrying. Sent with db_busy and db_pool_timeout.