Skip to main content
GET
List your loads
The loads your brokerage posted through this API, newest first: each one’s status, lane, equipment, dates, rates and outreach counts. Any rep’s key at the brokerage sees all of them; loads from your TMS or the dashboard aren’t listed. For a load’s offers, call GET /v1/loads/{id}. Pages: limit loads at a time (1 to 100, default 25). When there are more, next_cursor is set: send it back as cursor for the next page. It is null on the last page.

Authorizations

Authorization
string
header
required

One key per broker rep or per carrier signup. Keep it secret.

Query Parameters

limit
integer
default:25

How many loads per page, a whole number from 1 to 100. Defaults to 25. Anything else answers 400.

Required range: 1 <= x <= 100
cursor
string

The next_cursor from the previous page, sent with the same status and needs_decision as that page (other filters answer 400). Leave it out for the first page.

Maximum string length: 500
status
enum<string>

Only loads with this status. With sourcing or stalled, a page can hold fewer than limit loads even when more follow: keep paging until next_cursor is null.

Available options:
sourcing,
stalled,
covered,
inactive,
deleted
needs_decision
boolean

true: only open loads with offers waiting for your answer (offers.pending above 0). One call answers "anything new on my loads?" instead of reading every load. Send the cursor with the same filter.

Response

One page of loads, newest first.

loads
object[]
required

Newest first.

next_cursor
string | null
required

Send it as cursor for the next page. null on the last page.

next_step
string
required

For the agent. Exactly what to do next and which MCP tool to call (REST path in brackets).