Kargo · OAuth Scopes

Kargo OAuth Scopes

OAuth 2.0 probed

Kargo 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://mykargo.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.

CompanyLogisticsSupply ChainWarehouseComputer VisionArtificial IntelligenceShippingInventoryIndustrial AutomationFreightGraphQLWebhooks

Scopes: 0 Flows: clientCredentials Method: probed

OAuth endpoints

Token URL
https://mykargo.us.auth0.com/oauth/token

Flows
clientCredentials

Scopes (0)

Kargo 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.

📄 Provider scope reference: https://docs.kargo.ai/authentication

Source

OAuth Scopes

generated: '2026-08-23'
method: probed
source: https://mykargo.us.auth0.com/.well-known/openid-configuration
docs: https://docs.kargo.ai/authentication
summary:
  api_scopes_published: false
  note: 'Kargo''s public API uses the OAuth 2.0 client-credentials grant with an
    `audience` of https://api.kargo.zone/public_graphql and no `scope` parameter.
    Kargo publishes no scope or permission reference for the API audience, so there
    are no API scopes to record. Authorization is enforced per business/facility on
    the token (the OpenAPI documents a 403 "Token lacks permission for the given
    business/facility"), not by scope.'
schemes:
- name: auth0-client-credentials
  source: https://docs.kargo.ai/authentication
  flows:
  - flow: clientCredentials
    tokenUrl: https://mykargo.us.auth0.com/oauth/token
    audience: https://api.kargo.zone/public_graphql
scopes: []
authorization_server_scopes_supported:
  note: 'These are the OIDC scopes advertised by Kargo''s Auth0 tenant discovery
    document for interactive sign-in to the Kargo dashboard. They are Auth0 standard
    OIDC scopes and do NOT gate the public API audience.'
  values:
  - openid
  - profile
  - offline_access
  - name
  - given_name
  - family_name
  - nickname
  - email
  - email_verified
  - picture
  - created_at
  - identities
  - phone
  - address

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/kargo-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 email required.

GitHub Google LinkedIn

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