DispatchHealth · OAuth Scopes

DispatchHealth OAuth Scopes

OAuth 2.0 probed

DispatchHealth publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the DispatchHealth API on a user’s behalf.

Tokens are issued from https://www.dispatchhealth.com/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyHealthcareHealth SystemsHospital at HomeHome HealthUrgent CareCare DeliveryMedical ServicesTelehealthDigital Health

Scopes: 1 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://www.dispatchhealth.com/oauth/authorize

Token URL
https://www.dispatchhealth.com/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp	Access the MCP server at https://www.dispatchhealth.com/wp-json/mcp/mcp-oauth-server	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-31'
method: probed
source: https://www.dispatchhealth.com/.well-known/oauth-authorization-server
docs: null
schemes:
- name: MCPOAuth2
  source: well-known/dispatchhealth-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://www.dispatchhealth.com/oauth/authorize
    tokenUrl: https://www.dispatchhealth.com/oauth/token
scopes:
- scope: mcp
  description: Access the MCP server at https://www.dispatchhealth.com/wp-json/mcp/mcp-oauth-server
  flows: [authorizationCode]
  sources:
  - well-known/dispatchhealth-oauth-authorization-server.json
  - well-known/dispatchhealth-oauth-protected-resource.json
notes: A single coarse scope is advertised by both the RFC 8414 authorization-server
  metadata and the RFC 9728 protected-resource metadata. No scope/permission reference
  page is published, and no finer-grained scopes were observed.