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 ManagementWebhookFinal Mile
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://dummy-unused-url.com
https://dummy-unused-url.com
Token URL
https://dummy-unused-url.com
https://dummy-unused-url.com
Flows
authorizationCode
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.
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.
Source
OAuth Scopes
Work with this as data
Every scope set 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 oauth scopes
4 MCP tools reach this
find_scopesBrowse and filter every scope set in the catalog.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 scope set
curl "https://apis.io/api/v1/scopes/onerail-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.