Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/workwave-regions-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: WorkWave Route Manager Callback Regions API
description: 'The WorkWave Route Manager (WWRM) REST API connects order-management systems to RouteManager''s route planning and optimization engine. It exposes resources for territories, depots, regions, companies, drivers, vehicles, orders, optimized routes (Time of Arrival), and GPS tracking. Requests that add, update, or delete data are asynchronous: they return a requestId immediately and the final outcome is delivered to a configured webhook callback URL. Authentication uses an API key (a UUID) passed either as the `key` query-string parameter or the `X-WorkWave-Key` HTTP header.'
termsOfService: https://www.workwave.com/terms-of-service/
contact:
name: WorkWave Support
url: https://www.workwave.com/contact-us/
version: '1.0'
servers:
- url: https://wwrm.workwave.com/api/v1
description: WorkWave Route Manager production API
security:
- ApiKeyHeader: []
- ApiKeyQuery: []
tags:
- name: Regions
description: Manage regions within a territory.
paths:
/territories/{territoryId}/regions:
parameters:
- $ref: '#/components/parameters/territoryId'
get:
operationId: listRegions
tags:
- Regions
summary: List regions in a territory.
responses:
'200':
description: A list of regions.
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Region'
post:
operationId: addRegions
tags:
- Regions
summary: Add one or more regions.
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Region'
responses:
'200':
$ref: '#/components/responses/AsyncAccepted'
put:
operationId: replaceRegions
tags:
- Regions
summary: Replace one or more regions.
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Region'
responses:
'200':
$ref: '#/components/responses/AsyncAccepted'
delete:
operationId: deleteRegions
tags:
- Regions
summary: Delete one or more regions.
responses:
'200':
$ref: '#/components/responses/AsyncAccepted'
components:
responses:
AsyncAccepted:
description: The asynchronous write request was accepted and queued. The response contains a requestId; the final outcome is delivered to the configured callback URL.
content:
application/json:
schema:
$ref: '#/components/schemas/AsyncResponse'
schemas:
Region:
type: object
properties:
id:
type: string
name:
type: string
color:
type: string
AsyncResponse:
type: object
description: Acknowledgement of an accepted asynchronous write request.
properties:
status:
type: string
example: OK
requestId:
type: string
description: Identifier used to correlate the eventual callback notification.
parameters:
territoryId:
name: territoryId
in: path
required: true
description: The territory identifier used by most calls.
schema:
type: string
securitySchemes:
ApiKeyHeader:
type: apiKey
in: header
name: X-WorkWave-Key
description: API key (UUID) supplied via the X-WorkWave-Key HTTP header.
ApiKeyQuery:
type: apiKey
in: query
name: key
description: API key (UUID) supplied via the `key` query-string parameter. Takes precedence over the header if both are present.