Get Transport Route Version History
Get Transport Route Version History
Retrieve the full audit trail of changes made to a transport route, with field-level diffs and user attribution
GET
Get Transport Route Version History
Get Transport Route Version History
Returns a paginated list of every change ever made to a transport route — who made it, when, and which fields were affected. Each entry covers one database transaction and includes achanges array that shows the before/after value for each tracked field.
Tracked fields: name, quantity, unit_id, start_date, transport_direction.
Request
Authentication
Supports both authentication methods:Your API key (use this or
Authorization)Example: sk_live_1234567890abcdefBearer JWT token (use this or
x-api-key)Example: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...Headers
Your organization UUIDExample:
a8315ef3-dd50-43f8-b7ce-d839e68d51faPath Parameters
The unique identifier (UUID) of the transport routeExample:
010ed3b6-b513-40f3-b9fe-0f0a338d9274Query Parameters
Page number (1-based)
Number of version entries per page
Response
List of version entries for the requested page. See Version Entry Fields below.
Total number of version entries across all pages
Current page number
Number of items per page
Version Entry Fields
Internal database transaction ID. Versions are returned newest-first (descending
transaction_id).Type of change:
CREATE, UPDATE, or DELETEISO 8601 timestamp of when the change was committed.
null for very old records pre-dating audit logging.ID of the user who made the change.
null for system-triggered changes.First name of the user who made the change
Last name of the user who made the change
Field-level diff for this version entry.
For
CREATE operations, old_value is always null and new_value contains the initial value of each tracked field. For UPDATE operations, only fields that actually changed are included in changes. For DELETE operations, changes is an empty array.Example
Successful Response
Common Errors
401 Unauthorized
Cause: Missing or invalid API key / JWT token403 Forbidden
Cause: The authenticated user is not a member of the organization404 Not Found
Cause: Route ID does not exist or belongs to a different organizationRelated Endpoints
Get Transport Route
Retrieve the current state of a transport route
Update Transport Route
Modify a transport route and its sections
List Transport Routes
Retrieve all transport routes with filtering and pagination
Transport Overview
Full data model and distance calculation reference

