Ryder System · OAuth Scopes

Ryder System OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://login.okta.com/oauth2/v1/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.

Fleet ManagementLogisticsSupply ChainTransportationTruckingFortune 500

Scopes: 1 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://login.okta.com/oauth2/v1/token

Flows
clientCredentials

Scopes (1)

Scope	Description	Flows
APIM	The single fixed scope Ryder documents for OAuth 2.0 token requests (both Client Credentials and Authorization Code flows) against its Okta-backed Azure API Management gateway; requests must set scope to APIM, with per-API access governed by the Ocp-Apim-Subscription-Key subscription key rather than granular scopes.

📄 Provider scope reference: https://developer.ryder.com/docs/authentication

Source

OAuth Scopes

generated: '2026-07-11'
method: searched
source: openapi/ryder-tm-shipment-api-openapi.yml
docs: https://developer.ryder.com/docs/authentication
schemes:
- name: oauth2
  source: openapi/ryder-tm-shipment-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://login.okta.com/oauth2/v1/token
scopes:
- scope: APIM
  description: The single fixed scope Ryder documents for OAuth 2.0 token requests
    (both Client Credentials and Authorization Code flows) against its Okta-backed
    Azure API Management gateway; requests must set scope to APIM, with per-API access
    governed by the Ocp-Apim-Subscription-Key subscription key rather than granular
    scopes.
  sources:
  - https://developer.ryder.com/docs/authentication
note: Ryder uses a fixed-scope OAuth model — the authentication docs document only
  the single scope APIM, with no granular per-permission scopes published (https://developer.ryder.com/docs/authentication).