Givebutter · OAuth Scopes

Givebutter OAuth Scopes

OAuth 2.0 probed

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

DonationsFundraisingNon-ProfitCRMPaymentsWebhookEventA2A
Scopes: 0 Flows: Method: probed

Scopes (0)

Givebutter 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

Raw ↑ 
generated: '2026-09-12'
method: probed
source: https://auth.givebutter.com/.well-known/oauth-authorization-server
docs: null
description: >-
  Givebutter runs an OAuth 2.1 authorization server at auth.givebutter.com. It is NOT used by the
  REST API — that takes a single account-level Bearer API key with no scopes. The scopes below are
  what the authorization server itself advertises in its RFC 8414 metadata, and they gate the MCP
  server at https://mcp.givebutter.com/mcp plus a Wix integration surface. No scope reference page
  exists in the documentation; these values were read from the live discovery document, which is the
  only place they are published.
authorization_server:
  issuer: https://auth.givebutter.com
  authorization_endpoint: https://auth.givebutter.com/oauth/authorize
  token_endpoint: https://auth.givebutter.com/oauth/token
  registration_endpoint: https://auth.givebutter.com/oauth/register
  grant_types_supported:
  - authorization_code
  - refresh_token
  response_types_supported:
  - code
  code_challenge_methods_supported:
  - S256
  token_endpoint_auth_methods_supported:
  - none
  - client_secret_basic
  - client_secret_post
  metadata_file: well-known/givebutter-oauth-authorization-server.json
  openid_configuration: well-known/givebutter-openid-configuration.json
scopes:
- name: mcp
  description: Access to the Givebutter MCP server at https://mcp.givebutter.com/mcp. Declared as the
    required scope in the RFC 9728 protected-resource document for that endpoint.
  surface: mcp
  source: https://mcp.givebutter.com/.well-known/oauth-protected-resource
- name: openid
  description: OpenID Connect sign-in; returns an ID token.
  surface: identity
- name: profile
  description: Basic profile claims on the ID token.
  surface: identity
- name: email
  description: Email claim on the ID token.
  surface: identity
- name: wix:account.read
  description: Read access to Givebutter account data for the Wix integration.
  surface: partner-integration
- name: wix:campaigns.read
  description: Read access to campaign data for the Wix integration.
  surface: partner-integration
scope_count: 6
notes:
- The REST API (api.givebutter.com/v1) has no OAuth scheme and no scopes — one key, full account
  access. An agent given a Givebutter API key holds every permission the account has.
- Scope granularity exists only on the OAuth/MCP path, and there the only scope is the coarse "mcp".
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/givebutter-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.