CARTO · OAuth Scopes

CARTO OAuth Scopes

OAuth 2.0 searched

CARTO publishes 4 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the CARTO API on a user’s behalf.

Tokens are issued from https://auth.carto.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.

CompanyDeveloper ToolsLocation IntelligenceGeospatialMapsSpatial AnalyticsData WarehouseGISAgents

Scopes: 4 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://auth.carto.com/authorize

Token URL
https://auth.carto.com/oauth/token

Flows
authorizationCodeclientCredentials

Scopes (4)

Scope	Description	Flows
openid	OIDC authentication; issue an ID token.
profile	Access the user's basic profile claims.
email	Access the user's email and email_verified claims.
offline_access	Issue a refresh token for long-lived access.

📄 Provider scope reference: https://docs.carto.com/carto-for-developers/key-concepts/authentication-methods

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: https://docs.carto.com/carto-for-developers/key-concepts/authentication-methods/oauth-access-tokens
docs: https://docs.carto.com/carto-for-developers/key-concepts/authentication-methods
note: >-
  CARTO authenticates the Cloud-Native API with OAuth 2.0 bearer tokens issued by
  the Auth0-backed identity provider (auth.carto.com) for the
  `carto-cloud-native-api` audience. API-resource permissions are carried on the
  token as the user's/M2M-client's granted access rather than a fixed public scope
  registry; the OIDC identity scopes below come verbatim from the auth server's
  discovery document.
schemes:
- name: OAuth2
  source: well-known/cartodb-oauth-authorization-server.json
  audience: carto-cloud-native-api
  flows:
  - flow: authorizationCode
    authorizationUrl: https://auth.carto.com/authorize
    tokenUrl: https://auth.carto.com/oauth/token
  - flow: clientCredentials
    tokenUrl: https://auth.carto.com/oauth/token
scopes:
- scope: openid
  description: OIDC authentication; issue an ID token.
  sources: [well-known/cartodb-openid-configuration.json]
- scope: profile
  description: Access the user's basic profile claims.
  sources: [well-known/cartodb-openid-configuration.json]
- scope: email
  description: Access the user's email and email_verified claims.
  sources: [well-known/cartodb-openid-configuration.json]
- scope: offline_access
  description: Issue a refresh token for long-lived access.
  sources: [well-known/cartodb-openid-configuration.json]

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/cartodb-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.