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

WorkWave Routes API

Retrieve optimized routes and Time of Arrival data.

WorkWave Routes API is one of 11 APIs that WorkWave publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Routes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://wwrm.workwave.com/api/v1.

3 operations 3 paths 4 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://wwrm.workwave.com/api/v1
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

WorkWave Routes API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-WorkWave-Key (ApiKeyHeader). An API key is passed in the query as key (ApiKeyQuery). By default, every request must be authenticated.

  • ApiKeyHeader — API key (UUID) supplied via the X-WorkWave-Key HTTP header.
  • ApiKeyQuery — API key (UUID) supplied via the key query-string parameter. Takes precedence over the header if both are present.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Routes 3

Retrieve optimized routes and Time of Arrival data.

GET
/territories/{territoryId}/toa/routes
List optimized routes (Time of Arrival) for a territory.
listToaRoutes 1 param → 200
GET
/territories/{territoryId}/toa/routes/{routeId}
Retrieve a single optimized route with Time of Arrival details.
getToaRoute 2 params → 200404
GET
/territories/{territoryId}/approved/routes
Retrieve approved route plan data for a territory.
listApprovedRoutes 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Route (6 properties), RouteStep (5 properties), Location (3 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
RouteStep
object
5 properties
Route
object
6 properties
Location
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

workwave-routes-api-openapi.yml Raw ↑

Other APIs WorkWave publishes across the network.

WorkWave Callback API
WorkWave Companies API
WorkWave Depots API
WorkWave Drivers API
WorkWave GPS API
WorkWave Orders API
WorkWave Regions API
WorkWave Territories API
WorkWave Validation API
WorkWave Vehicles API
Where this information came from

This is an independent, third-party profile of WorkWave Routes 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.