Botkeeper · OAuth Scopes

Botkeeper OAuth Scopes

OAuth 2.0 probed

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

CompanyAccountingBookkeepingFinancial-ServicesArtificial IntelligenceAutomationSoftware-as-a-ServiceBanking DataPractice ManagementSmall Business

Scopes: 0 Flows: Method: probed

Scopes (0)

Botkeeper 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-08'
method: probed
source: https://cognito-idp.us-east-1.amazonaws.com/us-east-1_MZqyuuurX/.well-known/openid-configuration
name: Botkeeper OAuth / OIDC scopes
description: >-
  The only scopes Botkeeper publishes anywhere are the four standard OpenID
  Connect scopes advertised by its production Amazon Cognito user pool's
  discovery document. Botkeeper documents no resource-server scopes, no
  permission model, and no scope reference page. Nothing below is invented — the
  list is verbatim from scopes_supported in the discovery document.

authorization_server:
  issuer: https://cognito-idp.us-east-1.amazonaws.com/us-east-1_MZqyuuurX
  authorization_endpoint: https://login.auth.firm.ai/oauth2/authorize
  token_endpoint: https://login.auth.firm.ai/oauth2/token
  flows: [authorization_code, implicit]
  response_types_supported: [code, token]

scopes:
  - name: openid
    description: Standard OIDC scope — requests an ID token for the authenticated user.
    standard: true
  - name: email
    description: Standard OIDC scope — releases the email and email_verified claims.
    standard: true
  - name: phone
    description: Standard OIDC scope — releases the phone_number and phone_number_verified claims.
    standard: true
  - name: profile
    description: Standard OIDC scope — releases the standard profile claims.
    standard: true

custom_scopes: []

docs: null

gaps:
  - >-
    No resource-server (custom) scopes are advertised. The Botkeeper Partner
    Platform API on ipa.botkeeper.com is protected by an API Gateway authorizer,
    but no scope taxonomy for it is published.
  - No scopes/permissions reference page exists on botkeeper.com.
  - >-
    Least-privilege delegation is therefore not expressible against Botkeeper —
    a third party can only receive whole-user identity, not a scoped grant.

x-evidence:
  fetched: '2026-08-08'
  probes:
    - url: https://cognito-idp.us-east-1.amazonaws.com/us-east-1_MZqyuuurX/.well-known/openid-configuration
      status: 200
      content_type: application/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/botkeeper-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.