Donorbox API

Name: Donorbox 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.

Install Jentic One Beta

Connect the Donorbox API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Donorbox API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Donorbox 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

GET STARTED

Start building with Donorbox API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Donorbox 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 your Jentic One instance, 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 Jentic?

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

Credential isolation

Your Donorbox account email and API key are stored once, encrypted, by your own Jentic One instance and injected at execution time as HTTP Basic. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list donorbox donations' or 'list nonprofit donors', and Jentic returns the matching Donorbox operation with its parameter schema so the agent calls the right endpoint and paginates without reading the docs.

Time to first call

FAQs

Specific to using Donorbox 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.

Can I limit what my agent is allowed to do with the Donorbox API?

Yes. The Donorbox API is entirely read-only list endpoints, so with your self-hosted Jentic One instance you scope by operation and decide which of those reads the agent may call. You can allow it to list donations and donors while withholding campaigns, plans, events, or tickets, and because there are no write paths the agent can never create, refund, or edit anything. Your own rules govern which operations and stored credentials the agent uses, so a reporting agent only ever reaches the reads you put in its set.