Blameless · OAuth Scopes

Blameless OAuth Scopes

OAuth 2.0 probed

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

AIOpsSREIncident ManagementReliabilityService Level ObjectivesRetrospectivesOn-CallDevOps

Scopes: 0 Flows: Method: probed

Scopes (0)

Blameless 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:

Source

OAuth Scopes

generated: '2026-08-29'
method: probed
source: https://blamelesshq.auth0.com/.well-known/openid-configuration
specification: API Commons OAuth Scopes
specificationVersion: '0.1'
provider: Blameless
providerId: blameless
description: >-
  Scopes advertised by the Blameless Auth0 identity tenant's OIDC discovery document,
  fetched 2026-08-29. IMPORTANT: these are the tenant's standard OIDC identity scopes, not
  Blameless API permission scopes. Blameless' API authorization was rule-based
  (named rules such as IncidentRead), and that rule catalogue was published only on
  docs.blameless.com, which no longer resolves — so no API scope list can be recovered.
  Nothing here is derived from an OpenAPI; Blameless never published one.
issuer: https://blamelesshq.auth0.com/
authorization_endpoint: https://blamelesshq.auth0.com/authorize
token_endpoint: https://blamelesshq.auth0.com/oauth/token
grant_types_supported:
  - client_credentials
  - authorization_code
  - refresh_token
  - password
  - implicit
  - urn:ietf:params:oauth:grant-type:device_code
  - urn:ietf:params:oauth:grant-type:token-exchange
  - urn:ietf:params:oauth:grant-type:jwt-bearer
code_challenge_methods_supported:
  - S256
  - plain
scopes:
  - name: openid
    kind: oidc
    description: Standard OIDC scope requesting an ID token.
  - name: profile
    kind: oidc
    description: Basic profile claims.
  - name: offline_access
    kind: oidc
    description: Requests a refresh token.
  - name: email
    kind: oidc
  - name: email_verified
    kind: oidc
  - name: name
    kind: oidc
  - name: given_name
    kind: oidc
  - name: family_name
    kind: oidc
  - name: nickname
    kind: oidc
  - name: picture
    kind: oidc
  - name: phone
    kind: oidc
  - name: address
    kind: oidc
  - name: created_at
    kind: oidc
  - name: identities
    kind: oidc
api_scopes:
  count: 0
  note: >-
    No Blameless API scope catalogue is recoverable. The API used named access-control
    rules rather than OAuth scopes, and the page documenting them is gone.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

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