LeoLabs · OAuth Scopes

LeoLabs OAuth Scopes

OAuth 2.0 searched

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

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.

CompanySpaceSatellitesSpace Situational AwarenessSpace Traffic ManagementOrbital DataRadarAerospaceDefenseGeospatial

Scopes: 0 Flows: Method: searched

Scopes (0)

LeoLabs 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://auth.leolabs.space/.well-known/openid-configuration

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: https://auth.leolabs.space/.well-known/openid-configuration
docs: https://auth.leolabs.space/.well-known/openid-configuration
applies_to: LeoLabs Platform / documentation interactive sign-in (Okta org authorization
  server). The v1 Platform API itself is authenticated with a LeoLabs access key + secret
  key pair and exposes NO OAuth scope surface — see authentication/leo-labs-authentication.yml.
authorization_server:
  provider: Okta
  issuer: https://auth.leolabs.space
  authorization_endpoint: https://auth.leolabs.space/oauth2/v1/authorize
  token_endpoint: https://auth.leolabs.space/oauth2/v1/token
  userinfo_endpoint: https://auth.leolabs.space/oauth2/v1/userinfo
  jwks_uri: https://auth.leolabs.space/oauth2/v1/keys
  registration_endpoint: https://auth.leolabs.space/oauth2/v1/clients
  pkce_methods:
  - S256
  grant_types:
  - authorization_code
  - implicit
  - refresh_token
  - password
  - urn:ietf:params:oauth:grant-type:device_code
  - urn:openid:params:grant-type:ciba
  token_endpoint_auth_methods:
  - client_secret_basic
  - client_secret_post
  - client_secret_jwt
  - private_key_jwt
  - none
scopes:
- name: openid
  description: Required for OpenID Connect; requests an ID token.
- name: email
  description: The user's email address and its verification status.
- name: profile
  description: Default profile claims for the user.
- name: address
  description: The user's postal address claim.
- name: phone
  description: The user's phone number claim.
- name: offline_access
  description: Issues a refresh token so the client can renew access without the user present.
- name: groups
  description: The Okta groups the user belongs to.
notes:
- These are the standard OpenID Connect and Okta org-authorization-server scopes advertised
  by LeoLabs' discovery document. LeoLabs does not publish product-specific API 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.

All 92 tools

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/leo-labs-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.