The API Report CardAPI Index
OnFleet

OnFleet API

Delivery Management · onfleet.com

OnFleet's public REST API is self-serve with docs at docs.onfleet.com, scoped API keys, and 14+ HMAC-signed webhook events. Official SDKs cover Node, Python, and Ruby. A hard 20 requests per second org-wide cap forces batching on bulk jobs, and route optimization is Enterprise-plan only.

Last verified: October 2026Logistics & Supply ChainNO MCP
API GRADE
A
VERIFIED OCT 2026

SCORECARD

ExistenceGOODA public REST API covers tasks, workers, teams, hubs, vehicles, route plans, containers, destinations, and webhooks.
AccessGOODAPI keys generate self-serve in the dashboard under API & Webhooks; route optimization endpoints need the Enterprise plan.
CoverageGOODTasks with batch endpoints, workers, teams, route plans, optimization, manifests, custom fields, and metadata search.
AuthGOODScoped API keys over HTTP Basic; webhooks sign payloads with per-webhook HMAC secrets. No OAuth flow for third-party apps.
Docs & DXGOODOfficial Node, Python, and Ruby SDKs (Node ships a rate limiter), an llms.txt index, and 14+ documented webhook triggers.
StabilityGOOD
MCPNONENo official or community MCP server was found for Onfleet. Searches of MCP registries and GitHub returned no server for its delivery API. VERIFIED 2026-08
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

OnFleet scores A on Supergood's API Report Card. OnFleet's public REST API is self-serve with docs at docs.onfleet.com, scoped API keys, and 14+ HMAC-signed webhook events. Official SDKs cover Node, Python, and Ruby. A hard 20 requests per second org-wide cap forces batching on bulk jobs, and route optimization is Enterprise-plan only.

Tried to integrate with OnFleet?
SOURCES
**20 requests/second** is a hard org-wide ceiling, large back-fills or multi-team integrators must use batch endpoints or staggered jobs to avoid 429s and bans docs.onfleet.com ↗
Authentication is **HTTP Basic Auth with an API key**, no OAuth 2.0 / SSO flow for third-party app builders docs.onfleet.com ↗
**Route optimization API** (standard, auto-dispatch, vehicle-based) is Enterprise-plan-exclusive docs.onfleet.com ↗
Webhooks are single-trigger-per-entry (one webhook URL per event type), forcing fan-out or a routing proxy on the integrator side docs.onfleet.com ↗
Zapier integration is functional but reviewers report "lots of issues" with reliability for some triggers zapier.com ↗
No GraphQL surface, all integrations are REST + webhook docs.onfleet.com ↗
API access is included on all paid plans but webhook/scoped-key features and advanced search by metadata expand on higher tiers onfleet.com ↗
Bulk task creation is supported but the batch endpoint has its own size limits requiring chunking for very large imports docs.onfleet.com ↗
Task-volume-based pricing creates steep step-ups, moving from Scale ($1,349) to Enterprise ($3,099+) is ~$1,750/month more, expensive for growing fleets onfleet.com ↗
Many "commonplace" features (multi-brand, multi-region, SSO, auto-dispatch on lower tiers) are paid add-ons or Enterprise-only capterra.com ↗
No mobile-native dispatcher dashboard, only a responsive web UI for ops capterra.com ↗
Driver pay integrations and driver self-pickup of tasks are missing or limited capterra.com ↗
SMS/telephony usage is metered separately from task allotments and can add material cost locus.sh ↗
Dutchie integration rated only 3.0/5 by users; cannabis operators report setup friction support.dutchie.com ↗
Reporting history retention is tier-gated (90 days on Launch, 1 year on Scale, lifetime on Enterprise) onfleet.com ↗
Customers report headcount and support churn after the 2023 layoffs (~27% YoY headcount decline reported) tracxn.com ↗