API documentation | API docs for agents | OpenAPI 3.1

resolve

ark.resolve_tracking_driver_conflict

Switches a visible active dispatch to the app-linked duplicate-phone driver and starts internal ARK Tracking in one workflow.

Availability: Expanded preview
Scopes: loads:dispatch
ARK permissions: 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

dispatchIdstringrequired

Visible active dispatch whose driver should be switched.

format: uuid

targetDriverIdstringrequired

App-linked driver ID suggested by the tracking conflict response.

format: uuid

emailCopiesTostring | null

max length: 1000

notesstring | null

max length: 5000

Example request

Shell

curl -X POST 'https://arktms.com/api/v1/loads/<loadId>/tracking/driver-conflict/resolve' \
  -H "Authorization: Bearer $ARK_API_TOKEN" \
  -H "Idempotency-Key: <unique-key>" \
  -H "Content-Type: application/json" \
  -d '{
  "dispatchId": "<dispatchId>",
  "targetDriverId": "<targetDriverId>"
}'

Success response

Resolved driver conflict and started tracking

objectstringrequired

okbooleanrequired

api_versionstringrequired

request_idstringrequired

dataobjectrequired

data.loadIdstringrequired

format: uuid

data.loadobjectrequired

data.dispatchIdstringrequired

format: uuid

data.driverSwitchedbooleanrequired

data.driverobjectrequired

data.trackingobjectrequired

Errors

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