Get Trips By Registration
GET/trips/:registration
Returns a paginated list of trips for a specific vehicle, identified by its license plate, that overlap the specified time range.
A trip is included if it was active at any point within the requested window —
this means a trip that started before start_timestamp but ended within
the range will be included, and a trip that started within the range but
ended after end_timestamp will also be included. As a result, returned trips
may have start_timestamp or end_timestamp values that fall outside the
requested range and may span across different calendar dates.
The lookup window is limited to a maximum of 31 days between
start_timestamp and end_timestamp.
Data is available for approximately the last 5 years. Requests with
start_timestamp earlier than 5 years ago will be rejected with a 422 error.
A page beyond the end of the available data returns an empty result set rather
than an error.
Note: If you are computing total distance travelled for a specific day by summing
trip_distance, the result may be inaccurate. Trips that started beforestart_timestampor ended afterend_timestampare included in full, so their distance will be over- or under-counted relative to the requested window. For accurate daily distance figures, useGET /vehicles/{registration}/odometerinstead.
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.