Donorbox API

Name: Donorbox API API
Brand: Donorbox API
Availability: InStock

✓ Official Vendor SpecPaymentsBilling Subscriptionsbasic6 EndpointsREST

For Agents

Pull campaigns, donations, plans, donors, events, and tickets from a Donorbox account using HTTP Basic authentication for nonprofit reporting and CRM sync.

Quickstart

Get started with Donorbox API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list donorbox donations"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Donorbox API API.

List active and past campaigns via GET /api/v1/campaigns

Pull individual donation records through GET /api/v1/donations

Retrieve recurring donation plans with GET /api/v1/plans

List donor records via GET /api/v1/donors

Fetch fundraising events through GET /api/v1/events

GET STARTED

Start building with Donorbox API API

Explore with Jentic

View OpenAPI Document

The Donorbox API exposes read-only access to fundraising data managed inside Donorbox accounts: campaigns, donations, recurring donation plans, donors, events, and event tickets. Each endpoint returns a paginated JSON list and authenticates with HTTP Basic using the account email and API key. The API is suited to nonprofit reporting, donor CRM sync, and accounting reconciliation workflows where structured donation history needs to flow into another system without manual export.

Use Cases

Patterns agents use Donorbox API API for, with concrete tasks.

★ Donor CRM Sync

Sync donor and donation records into a CRM by polling GET /api/v1/donors and GET /api/v1/donations on a schedule. The Donorbox API returns paginated lists with stable IDs, so an integration can upsert records into the CRM without losing historical context. A daily sync job is straightforward to build.

GET /api/v1/donors with pagination, then for each donor GET /api/v1/donations filtered by donor email, and upsert into the nonprofit CRM.

Accounting Reconciliation

Reconcile Donorbox donations against accounting ledgers by pulling GET /api/v1/donations and matching transaction amounts and dates. Recurring donations from /api/v1/plans contextualise expected-versus-actual amounts so finance teams can spot missed renewals.

GET /api/v1/donations for the prior month and produce a CSV grouped by campaign for accounting import.

Event and Ticket Reporting

Generate event reports by combining GET /api/v1/events with GET /api/v1/tickets, producing attendance rosters and revenue totals per event. This supports gala planning, capacity management, and post-event thank-you communications.

GET /api/v1/events for the next 60 days, then GET /api/v1/tickets for each event and produce an attendance roster.

AI Agent Nonprofit Reporting via Jentic

An AI agent uses Jentic to look up Donorbox endpoints, executes the read calls, and produces summaries for nonprofit staff (top donors, recent gifts, recurring churn). Donorbox Basic credentials stay in the Jentic vault, so the agent never holds the API key while iterating over donor lists.

Search Jentic for 'list donorbox donations', execute GET /api/v1/donations for the last week, and return a summary of total raised and top three donors.

Key Endpoints

6 endpoints — the donorbox api exposes read-only access to fundraising data managed inside donorbox accounts: campaigns, donations, recurring donation plans, donors, events, and event tickets.

METHOD

PATH

DESCRIPTION

GET

/api/v1/campaigns

List campaigns

GET

/api/v1/donations

List donations

GET

/api/v1/plans

List recurring donation plans

GET

/api/v1/donors

List donors

GET

/api/v1/events

List events

GET

/api/v1/tickets

List event tickets

GET

/api/v1/campaigns

List campaigns

GET

/api/v1/donations

List donations

GET

/api/v1/plans

List recurring donation plans

GET

/api/v1/donors

List donors

GET

/api/v1/events

List events

GET

/api/v1/tickets

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Donorbox account email and API key are stored encrypted in the Jentic vault and applied as HTTP Basic at execution time. Agents see only a scoped reference, so /api/v1/donations and /api/v1/donors calls never expose the raw key.

Intent-based discovery

Agents search Jentic for intents like 'list donorbox donations' or 'list nonprofit donors' and receive the matching Donorbox operation with its parameter schema, ready to execute and paginate.

Time to first call

Direct integration: half a day for auth, pagination, and sync logic. Through Jentic: under 30 minutes from search to first synced page.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Stripe

Underlying payment processing

Use Stripe alongside Donorbox to access raw charge and dispute data that Donorbox does not surface.

Alternative

PayPal Orders

Payment processing for one-time and recurring donations

Use PayPal directly when the nonprofit collects donations through PayPal rather than Donorbox.

Complementary

Brevo

Email and CRM platform

Combine Donorbox donor exports with Brevo for thank-you and stewardship campaigns.

FAQs

Specific to using Donorbox API API through Jentic.

What authentication does the Donorbox API use?

HTTP Basic authentication. Use your Donorbox account email as the username and the API key from your Donorbox dashboard as the password. Through Jentic, both values are stored encrypted in the vault and the Basic header is constructed at execution time so the agent never holds the raw key.

Can I list every donation with the Donorbox API?

Yes. GET /api/v1/donations returns donation records with pagination. Filter by donor email or date range as supported by Donorbox parameters to scope a sync window for accounting reconciliation.

What are the rate limits for the Donorbox API?

The OpenAPI spec does not declare explicit rate limits. Donorbox documents practical per-account caps; throttle to a few requests per second, page through results, and apply exponential backoff on 429 responses for nightly sync jobs.

How do I sync donors through the Donorbox API via Jentic?

Run pip install jentic and search for 'list donorbox donors'. Jentic returns GET /api/v1/donors with its pagination schema; execute it and Jentic injects the Basic credential from the vault. Pair with /api/v1/donations to enrich each donor with gift history.

Can I retrieve recurring donation plans?

Yes. GET /api/v1/plans returns active recurring plans on the account, including amount, interval, and donor reference, useful for tracking churn and expected monthly revenue.

Does the Donorbox API expose event ticket sales?

Yes. GET /api/v1/events lists fundraising events and GET /api/v1/tickets lists ticket purchases. Combine the two to produce attendance rosters or post-event thank-you mailings.