The Stops API manages the individual pickup and delivery locations that make up a load’s route. Each stop is linked to a load, assigned to a truck and driver, and carries an appointment date that determines its position in the route. As drivers progress through the route, stops advance through check-in, check-out, and completion states. On check-in, the system automatically sets the next uncompleted stop as the current heading. Base URL:Documentation Index
Fetch the complete documentation index at: https://mintlify.com/ShohjahonSohibov/repo-for-agent/llms.txt
Use this file to discover all available pages before exploring further.
/api/stops
Required permission (minimum): Stops.View
Endpoints
GET /api/stops
List stops with optional filters. RequiresStops.View.
Query parameters
Filter stops by load ID.
Filter by completion state:
completed or pending.Filter to pickup stops (
true) or delivery stops (false).Page number, 1-indexed. Defaults to
1.Items per page. Defaults to
20, maximum 100.cURL
GET /api/stops/
Get details for a single stop. RequiresStops.View.
Path parameters
The stop ID.
cURL
Response
The
isCurrent field in the response maps from the internal IsCurrentHeading flag on the Stop entity. It is true when this stop is the one the truck is actively heading toward.POST /api/stops
Create a new stop and attach it to a load. RequiresStops.Create.
Request body
The load this stop belongs to.
true for a pickup stop, false for a delivery stop.ISO 8601 scheduled appointment date and time. Stops are ordered by this field when determining route sequence.
ID of the address record for this stop location.
Explicit display order override. When omitted, order is derived from
appointmentDate.The truck ID assigned to service this stop.
Array of driver IDs (
Driver.Id as strings) assigned to this stop. Do not use ImportId.PUT /api/stops/
Update a stop’s properties. RequiresStops.Update.
Path parameters
The stop ID to update.
POST /api/stops. Include only the fields you want to change.
cURL
DELETE /api/stops/
Delete a stop from a load. RequiresStops.Delete.
Path parameters
The stop ID to delete.
cURL
PUT /api/stops//checkin
Mark a stop as checked in — the driver has arrived. RequiresStops.Update.
Path parameters
The stop ID.
Auto-advance on check-in: When a stop is checked in, the system automatically updates the current heading:
- Clears
IsCurrentHeading = falseon the checked-in stop. - Finds the next uncompleted stop on the same load and truck, ordered by
AppointmentDate. - Sets
IsCurrentHeading = trueon that stop. - If no next stop exists (last stop on the load), the heading is left unset.
isCurrent: false on the checked-in stop after this auto-advance.PUT /api/stops//checkout
Mark a stop as checked out — the driver has departed. RequiresStops.Update.
Path parameters
The stop ID.
cURL
Response
PUT /api/stops//complete
Mark a stop as fully completed. RequiresStops.Update.
Path parameters
The stop ID.
cURL
Stop fields reference
| Field | Type | Description |
|---|---|---|
loadId | number | Load this stop belongs to |
isPickup | boolean | true = pickup stop, false = delivery stop |
isCompleted | boolean | Whether the stop has been fully completed |
isCurrent | boolean | Whether the truck is currently heading to this stop (maps from IsCurrentHeading) |
appointmentDate | string | Scheduled appointment — determines route order |
order | number | Display order, derived from appointmentDate if not set explicitly |
addressId | number | Linked address with geocoded coordinates |
assignedTruckId | number | Truck responsible for this stop |
assignedDriverIds | string[] | Driver IDs (Driver.Id, not ImportId) assigned to this stop |
checkIn | string | null | ISO 8601 timestamp when the driver checked in |
checkOut | string | null | ISO 8601 timestamp when the driver checked out |
Permissions summary
| Permission | Grants access to |
|---|---|
Stops.View | GET endpoints |
Stops.Create | POST /api/stops |
Stops.Update | PUT, check-in, check-out, complete |
Stops.Delete | DELETE /api/stops/{id} |