API documentation | API docs for agents | OpenAPI 3.1
GET /api/v1/loads
ark.search_loads
Searches active loads visible to the connected actor by load number, reference fields, customer, status, and team. Exact load-number, PO, BOL, pickup-number, and stop-reference matches are selected before fuzzy active matches and can return deleted loads with status Deleted. Active exact matches remain first when a reference is shared; broad and fuzzy matches remain active-only.
- Availability
- Core preview
- Scopes
loads:read- ARK permissions
canViewLoads- Team visibility
- Required and enforced
- Idempotency-Key
- Not required
- Approval
- No MCP approval on REST API-token calls
- Rate limit
- API credential and organization budgets
Parameters
qquerystring- Broad and fuzzy matching searches active loads only. An exact load number or reference can also match a deleted load.
- min length: 1; max length: 100
statusquerystring- Filters active loads by status. With an exact load-number or reference search, Deleted returns only deleted matches.
- min length: 1; max length: 50
team_idsquerystring- Comma-separated team IDs. Omit to use all teams visible to the connected user.
limitqueryinteger- default: 25; min: 1; max: 100
cursorquerystring
Request body
None.
Example request
Shell
curl 'https://arktms.com/api/v1/loads' \
-H "Authorization: Bearer $ARK_API_TOKEN"Success response
Visible load search results
objectstringrequiredokbooleanrequiredapi_versionstringrequiredrequest_idstringrequireddataobjectrequireddata.itemsarray<object>requireddata.paginationobjectrequiredErrors
HTTP 400- Invalid request
HTTP 401- Authentication required
HTTP 403- Permission, scope, team, or entitlement denied