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

Dispatch Users API

Dispatchers and technicians using the Dispatch applications.

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

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

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

Requests are made against 2 base URLs: https://files-api.dispatch.me, https://files-api-sandbox.dispatch.me.

6 operations 3 paths 2 schemas 1 DELETE2 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1
Base URL
https://api.dispatch.me
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

Dispatch Users API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 bearer token obtained from the core API at POST /v3/oauth/token.

Paths & Operations 6

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

Users 6

Dispatchers and technicians using the Dispatch applications.

POST
/v3/users
Create a user
createUser body → 201401403422
GET
/v3/users
List users
listUsers 5 params → 200401
GET
/v3/users/{id}
View a single user
getUser 1 param → 200401404
PATCH
/v3/users/{id}
Update a user
updateUser 1 param body → 200401404422
DELETE
/v3/users/{id}
Delete / deactivate a user
deactivateUser 1 param → 204401404
POST
/v3/users/{id}/restore
Reactivate a user
reactivateUser 1 param → 200401404

Schemas 2

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

Location
object
Locations are not business objects, but attributes on several core objects. Dispatch currently supports locations in the US and Canada only.
6 properties 2 required
User
object
10 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dispatch-users-api-openapi.yml Raw ↑

Other APIs Dispatch publishes across the network.

Dispatch Appointments API
Dispatch Authentication API
Dispatch Brands API
Dispatch Customers API
Dispatch Files API
Dispatch Jobs API
Dispatch Organizations API
Dispatch Sources API
Dispatch Survey Responses API
Dispatch Work Orders API
Where this information came from

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