Abatable · OAuth Scopes

Abatable OAuth Scopes

OAuth 2.0 probed

Abatable publishes 14 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Abatable API on a user’s behalf.

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

Carbon MarketsCarbon CreditsCarbon OffsetsEnvironmental AssetsVoluntary Carbon MarketCORSIAClimateSustainabilityNet ZeroProcurementMarket IntelligenceDue DiligenceESGMCP

Scopes: 14 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://login.abatable.com/authorize

Token URL
https://login.abatable.com/oauth/token

Flows
authorizationCode

Scopes (14)

Scope	Description	Flows
openid	OIDC authentication; issue an ID token	authorizationCode
profile	Basic profile claims	authorizationCode
email	Email address claim	authorizationCode
email_verified	Email verification status claim	authorizationCode
offline_access	Issue a refresh token	authorizationCode
name	Full name claim	authorizationCode
given_name	Given name claim	authorizationCode
family_name	Family name claim	authorizationCode
nickname	Nickname claim	authorizationCode
picture	Profile picture claim	authorizationCode
phone	Phone number claim	authorizationCode
address	Address claim	authorizationCode
created_at	Account creation timestamp claim	authorizationCode
identities	Linked identity provider records claim	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-05'
method: probed
source: https://login.abatable.com/.well-known/openid-configuration
docs: null
docs_note: >-
  Abatable publishes no scopes or permissions reference. The scopes below are the
  `scopes_supported` array its Auth0 OIDC discovery document advertises — the standard OIDC claim
  scopes plus Auth0's profile-claim scopes. They are identity scopes, not API authorisation
  scopes: no Abatable-specific resource scope (read:*, write:*) is published anywhere, and the
  Cloudflare Access authorization server that guards the MCP endpoint publishes no
  `scopes_supported` at all.
schemes:
- name: Auth0 OIDC
  source: well-known/abatable-login-openid-configuration.json
  issuer: https://login.abatable.com/
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.abatable.com/authorize
    tokenUrl: https://login.abatable.com/oauth/token
- name: Cloudflare Access (MCP)
  source: well-known/abatable-mcp-oauth-authorization-server.json
  issuer: https://abatable.cloudflareaccess.com
  scopes_supported_published: false
scopes:
- {scope: openid, description: OIDC authentication; issue an ID token, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: profile, description: Basic profile claims, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: email, description: Email address claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: email_verified, description: Email verification status claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: offline_access, description: Issue a refresh token, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: name, description: Full name claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: given_name, description: Given name claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: family_name, description: Family name claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: nickname, description: Nickname claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: picture, description: Profile picture claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: phone, description: Phone number claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: address, description: Address claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: created_at, description: Account creation timestamp claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
- {scope: identities, description: Linked identity provider records claim, flows: [authorizationCode], sources: [well-known/abatable-login-openid-configuration.json]}
resource_scopes:
  published: false
  note: >-
    No resource/permission scope vocabulary is published. An integrator cannot tell from any public
    surface what an Abatable access token is authorised to do.

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