Skip to main content
Every Developer API endpoint requires a specific scope. Scopes are enabled at the organization level. All projects and API keys under an organization inherit its enabled scopes.

​
Available scopes

ScopeDescription
coreAccess to charities, chains, token data, and config read/delete
partnerCreate/list donation configs, view source leaderboard data
Scopes are modular, not hierarchical. Having partner does not automatically grant core, and vice versa. Your organization needs each scope explicitly enabled for the endpoints it needs.

​
Default scopes

New organizations are provisioned with the core scope by default. To enable additional scopes, contact us at support@donate.gg.

​
Endpoints by scope

​
core

Core endpoints allow developers to fetch public information and inspect or delete configs by ID.
MethodEndpointDescription
GET/charitiesList charities
GET/charities/searchSearch charities
GET/charities/{charityId}Get a charity by ID
GET/chainsList supported chains
GET/{chainId}/tokens/{address}Get a token by address
GET/{chainId}/tokens/leaderboardToken leaderboard
GET/configs/{configId}Get a config by ID
DELETE/configs/{configId}Delete a config

​
partner

Partner endpoints are reserved for full integration partners, enabling config creation/listing and source leaderboard access.
MethodEndpointDescription
GET/configsList configs
POST/configsCreate a config
GET/{chainId}/donationSources/{address}/subjects/leaderboardSource subject leaderboard

​
Error response

If you call an endpoint that requires a scope your organization doesn’t have, the API returns a 403: 
{
  "error": "API scope 'partner' is not enabled for this organization",
  "code": "SCOPE_DENIED"
}
StatusCodeDescription
403SCOPE_DENIEDThe required scope is not enabled for your organization
Rate limiting runs before scope checks. A SCOPE_DENIED response still counts against your rate limit.