NEXT Trucking · OAuth Scopes

NEXT Trucking OAuth Scopes

OAuth 2.0 probed

NEXT Trucking publishes 14 OAuth 2.0 scopes via the authorization_code and client_credentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the NEXT Trucking API on a user’s behalf.

Tokens are issued from https://prod-nexttrucking.us.auth0.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.

CompanyLogisticsFreightTruckingDrayageSupply ChainTransportationMarketplaceTransportation ManagementShipping

Scopes: 14 Flows: authorization_code, client_credentials Method: probed

OAuth endpoints

Authorization URL
https://prod-nexttrucking.us.auth0.com/authorize

Token URL
https://prod-nexttrucking.us.auth0.com/oauth/token

Flows
authorization_codeclient_credentials

Scopes (14)

Scope	Description	Flows
openid	Request an ID token (OpenID Connect).
profile	Basic profile claims for the authenticated user.
offline_access	Issue a refresh token.
name	The user's full name claim.
given_name	The user's given name claim.
family_name	The user's family name claim.
nickname	The user's nickname claim.
email	The user's email address claim.
email_verified	Whether the user's email address has been verified.
picture	The user's profile picture claim.
created_at	Account creation timestamp claim.
identities	Linked identity providers for the account.
phone	The user's phone number claim.
address	The user's address claim.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: >-
  scopes_supported in https://prod-nexttrucking.us.auth0.com/.well-known/openid-configuration
  (HTTP 200, saved verbatim to well-known/next-trucking-openid-configuration.json).
docs: null
summary: >-
  The only scope set NEXT Trucking exposes anonymously is the stock OpenID Connect profile advertised
  by its Auth0 tenant. These are identity scopes, NOT application permissions: nothing here grants
  access to loads, quotes, trips, documents or any ATLAS resource. No API permission reference is
  published, and the resource scopes the ATLAS gateway actually enforces are not discoverable without
  credentials.
provider: auth0
issuer: https://prod-nexttrucking.us.auth0.com/
flows:
  authorization_code:
    authorizationUrl: https://prod-nexttrucking.us.auth0.com/authorize
    tokenUrl: https://prod-nexttrucking.us.auth0.com/oauth/token
    pkce: S256
  client_credentials:
    tokenUrl: https://prod-nexttrucking.us.auth0.com/oauth/token
    note: Advertised, but no audience or third-party client registration is published.
scope_count: 14
scopes:
  - name: openid
    description: Request an ID token (OpenID Connect).
    kind: identity
  - name: profile
    description: Basic profile claims for the authenticated user.
    kind: identity
  - name: offline_access
    description: Issue a refresh token.
    kind: identity
  - name: name
    description: The user's full name claim.
    kind: identity
  - name: given_name
    description: The user's given name claim.
    kind: identity
  - name: family_name
    description: The user's family name claim.
    kind: identity
  - name: nickname
    description: The user's nickname claim.
    kind: identity
  - name: email
    description: The user's email address claim.
    kind: identity
  - name: email_verified
    description: Whether the user's email address has been verified.
    kind: identity
  - name: picture
    description: The user's profile picture claim.
    kind: identity
  - name: created_at
    description: Account creation timestamp claim.
    kind: identity
  - name: identities
    description: Linked identity providers for the account.
    kind: identity
  - name: phone
    description: The user's phone number claim.
    kind: identity
  - name: address
    description: The user's address claim.
    kind: identity
resource_scopes:
  published: false
  note: >-
    No NEXT-Trucking-specific API scopes (loads, containers, appointments, documents, payables) are
    published anywhere. The ATLAS gateway returns 401 to every anonymous request, so its authorization
    model cannot be introspected without credentials.

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.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/next-trucking-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.