OneRail · OAuth Scopes

OneRail OAuth Scopes

OAuth 2.0 derived

OneRail uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://dummy-unused-url.com.

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.

last-mile-deliverydelivery-orchestrationlogisticssupply-chainroute-optimizationcourier-networkshippingfleet-managementtransportationorder-managementwebhooksfinal-mile
Scopes: 0 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://dummy-unused-url.com
Token URL
https://dummy-unused-url.com
Flows
authorizationCode

Scopes (0)

OneRail implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

The Operations API declares an oauth2 securityScheme but publishes ZERO scopes: the flow object is empty and no operation carries an oauth2 security requirement with scopes. The spec itself states the authorizationUrl and tokenUrl values ("https://dummy-unused-url.com") are placeholders present only to satisfy the OpenAPI schema - OneRail validates access tokens minted by the customer's own IdP (e.g. Okta) and the real IdP URLs are configured out of band per deployment. No scopes or permissions reference page exists on the OneRail Developer Hub. The practical authorization model is the organization App ID / API Key pair plus platform roles (Location/Ops User, View Only, Global Admin) assigned in the UI - see authentication/onerail-authentication.yml.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-02'
method: derived
source: openapi/onerail-operations-api-openapi.yml
schemes:
- name: OAuth
  source: openapi/onerail-operations-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://dummy-unused-url.com
    tokenUrl: https://dummy-unused-url.com
  description: 'OAuth 2.0 access token validated by the Operations service (e.g. Okta-backed

    integrations). Clients obtain tokens from their own IdP outside of this API

    and call endpoints with `Authorization: OAuth <access_token>`. The

    `authorizationUrl` and `tokenUrl` values below are placeholders only to

    satisfy the OpenAPI schema; this service does not call them directly and the

    real IdP URLs are configured via environment and introspection logic in code.'
scopes: []
docs: null
note: 'The Operations API declares an oauth2 securityScheme but publishes ZERO scopes: the flow object
  is empty and no operation carries an oauth2 security requirement with scopes. The spec itself states
  the authorizationUrl and tokenUrl values ("https://dummy-unused-url.com") are placeholders present only
  to satisfy the OpenAPI schema - OneRail validates access tokens minted by the customer''s own IdP (e.g.
  Okta) and the real IdP URLs are configured out of band per deployment. No scopes or permissions reference
  page exists on the OneRail Developer Hub. The practical authorization model is the organization App
  ID / API Key pair plus platform roles (Location/Ops User, View Only, Global Admin) assigned in the UI
  - see authentication/onerail-authentication.yml.'
placeholder_urls: true
searched: https://developer.onerail.io/hc/en-us - no scopes/permissions reference published