The Giving Block · Authentication Profile

The Giving Block Authentication

Authentication

The Giving Block declares 1 security scheme(s) across its OpenAPI definitions.

CompanyCrypto Web3DonationsFundraisingNon-ProfitPaymentsCryptocurrencyStock DonationsWebhookWidgets

Methods: Schemes: 1 OAuth flows: API key in:

Security Schemes

Authorization http

scheme: bearer · in: header ()

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://docs.thegivingblock.com/reference/getting-started-1 (Authentication Flow)
docs: https://docs.thegivingblock.com/docs/authentication-flow
api: The Giving Block Public API
summary: >-
  JWT-based, token authentication. Partners request API user credentials (and AES
  encryption keys for webhook notifications) by emailing The Giving Block's integrations
  team. Credentials are exchanged at the login endpoint for a short-lived access token
  plus a refresh token; the access token is sent as a bearer token on every request and
  renewed via the refresh-tokens endpoint. Server-to-server integration.
schemes:
- id: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  in: header
  name: Authorization
  description: >-
    JWT access token obtained from POST /v1/login and refreshed via
    POST /v1/refresh-tokens. Sent as `Authorization: Bearer <accessToken>`.
flows:
- name: login
  operationId: login
  method: POST
  path: /v1/login
  description: Exchange issued API user credentials for an access token and refresh token.
- name: refreshTokens
  operationId: refreshTokens
  method: POST
  path: /v1/refresh-tokens
  description: Exchange a valid refresh token for a new access token.
credentials:
  provisioning: manual
  how: Email the integrations team to request API user credentials and AES webhook keys.
  environments:
  - name: production
    baseURL: https://public-api.tgbwidget.com
  - name: sandbox
    baseURL: https://public-api.sandbox.thegivingblock.com
notes:
- No OAuth2 authorization/token URLs are published; auth is a custom JWT login exchange.
- Webhook payloads are AES-256 encrypted using keys issued alongside API credentials.
- Common auth error codes include INVALID_JWT_TOKEN.

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

curl "https://apis.io/api/v1/security/the-giving-block-authentication"

All security posture

curl "https://apis.io/api/v1/security?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.