Dispatch last-mile delivery tasks to drivers using the Onfleet API
domain: onfleet.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate all requests using HTTP Basic Auth with your Onfleet API key as the username and an empty password
POST to https://onfleet.com/api/v2/tasks with a destination (address or lat/lng), recipient (name, phone), and optional notes, pickupTask flag, and completionRequirements (e.g. signature, photo)
Assign the task to a worker by including the worker field in the creation body, or leave it unassigned for auto-dispatch
Trigger auto-dispatch for a team by POST to https://onfleet.com/api/v2/teams/{teamId}/dispatch; Onfleet optimizes task assignment to on-duty drivers
Track driver location and task status in real time by listening to Onfleet webhooks (register via the dashboard or API) for task events such as taskStarted, taskCompleted, and taskFailed
Query GET https://onfleet.com/api/v2/tasks/{taskId} to retrieve the latest completion details including proof of delivery
Known gotchas
Onfleet auto-dispatch only assigns tasks to workers who are currently on duty; tasks will remain unassigned if no drivers in the team are clocked in, so verify team duty status before dispatching
The completionRequirements object must be set at task creation time; it cannot be added or modified after the task has been assigned or started
Phone numbers in the recipient object must include the country code in E.164 format; numbers without country codes are rejected or silently stored as invalid, preventing SMS notifications from being sent to customers
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?