API documentation | API docs for agents | OpenAPI 3.1
POST /api/v1/loads/{loadId}/tracking/notify
ark.send_load_location_notification
Sends a manual location-update notification for a visible load using configured tracking notification recipients and throttle rules.
- Availability
- Expanded preview
- Scopes
loads:write- ARK permissions
one of: canEditLoadone of: canAssignLoads- Team visibility
- Required and enforced
- Idempotency-Key
- Required for this write
- Approval
- No MCP approval on REST API-token calls
- Rate limit
- API credential and organization budgets
Parameters
loadIdpathstringrequired- format: uuid
Idempotency-Keyheaderstringrequired- Required for external write operations. Reuse the same key only for exact retries of the same request body.
- min length: 1; max length: 200
Request body
citystringrequiredmin length: 1; max length: 200
statestringrequiredmin length: 1; max length: 20
countrystringone of: USA, CAN, MEX; default: "USA"
latitudenumber | nullmin: -90; max: 90
longitudenumber | nullmin: -180; max: 180
timezoneIdstring | nullmax length: 100
locationDateTimestringformat: date-time
Example request
Shell
curl -X POST 'https://arktms.com/api/v1/loads/<loadId>/tracking/notify' \
-H "Authorization: Bearer $ARK_API_TOKEN" \
-H "Idempotency-Key: <unique-key>" \
-H "Content-Type: application/json" \
-d '{
"city": "<city>",
"state": "<state>"
}'Success response
Load location notification result
objectstringrequiredokbooleanrequiredapi_versionstringrequiredrequest_idstringrequireddataobjectrequireddata.loadIdstringrequiredformat: uuid
data.loadobjectrequireddata.locationobjectrequireddata.notificationSentbooleanrequireddata.notificationResultobjectrequiredErrors
HTTP 400- Invalid request
HTTP 401- Authentication required
HTTP 403- Permission, scope, team, or entitlement denied
HTTP 404- Resource not found
HTTP 409- Idempotency conflict or in-progress retry
HTTP 502- External provider or worker queue could not be reached