How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Onfleet Route Plans API

Create and manage route plans — ordered sequences of tasks assigned to a worker for a time window— and kick off asynchronous route optimization jobs (task-based, vehicle-based, or auto-dispatch).Optimization endpoints are an Enterprise plan feature; results delivered via therouteOptimizationJobCompleted webhook.

Onfleet Route Plans API is one of 9 APIs that Onfleet publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Last Mile Delivery, Route Optimization, and Route Plans. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, and 1 JSON Schema.

This API exposes 6 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 2.7.

Requests are made against a single base URL, https://onfleet.com/api/v2.

6 operations 3 paths 2 schemas 1 DELETE2 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.7
Base URL
https://onfleet.com/api/v2
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Onfleet Route Plans API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Route Plans 6
GET
/routePlans
List Route Plans
listRoutePlans 4 params → 200
POST
/routePlans
Create Route Plan
createRoutePlan body → 200
GET
/routePlans/{routePlanId}
Get Route Plan By ID
getRoutePlan 1 param → 200
PUT
/routePlans/{routePlanId}
Update Route Plan
updateRoutePlan 1 param body → 200
DELETE
/routePlans/{routePlanId}
Delete Route Plan
deleteRoutePlan 1 param → 200
PUT
/routePlans/{routePlanId}/tasks
Add Tasks To Route Plan
addTasksToRoutePlan 1 param body → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are RoutePlan (17 properties), RoutePlanCreate (12 properties). Each schema is shown below with its type and property counts.

RoutePlanCreate
object
12 properties 3 required
RoutePlan
object
17 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

onfleet-route-plans-api-openapi.yml Raw ↑

Other APIs Onfleet publishes across the network.

Onfleet Tasks API
Onfleet Workers API
Onfleet Orders API
Onfleet Organizations & Teams API
Onfleet Recipients API
Onfleet Destinations API
Onfleet Webhooks API
Onfleet Route Optimization API
Where this information came from

This is an independent, third-party profile of Onfleet Route Plans API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.