Keela API

Name: Keela API
Brand: Keela API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact Managementoauth210 EndpointsREST

For Agents

Manage donor contacts, households, campaigns, donations, revenues, tags, and impact areas inside a Keela nonprofit CRM tenant. 10 endpoints covering the core fundraising workflow.

Install Jentic One Beta

Connect the Keela API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Keela 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 Keela API.

Create and list donor contacts and households via /api/contacts and /api/households

Manage fundraising campaigns and their attribution sources via /api/campaigns and /api/sources

Record donations and other revenue via /api/donations and /api/revenues

GET STARTED

Start building with Keela API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Keela API for, with concrete tasks.

★ Donate-Widget to CRM Sync

Pipe gifts from a charity's website donate widget straight into Keela so finance and fundraising teams see donations the moment they land. The /api/contacts and /api/donations endpoints accept the donor and gift in two calls; combined with /api/sources for attribution, a small nonprofit can report 'gifts by acquisition source' without exporting and joining files in a spreadsheet.

Resolve or create the contact via POST /api/contacts, then record the gift via POST /api/donations with the source ID from the campaign tracking parameter.

Campaign Performance Reporting

Pull campaigns, donations, and sources from Keela into a BI dashboard so program directors can see fundraising velocity by campaign without logging into the CRM. /api/campaigns returns campaign metadata, /api/donations returns gifts by campaign ID, and /api/sources returns attribution. Combined nightly, a $250 BI tool replaces a $10K consulting engagement for many small charities.

List campaigns via GET /api/campaigns and donations via GET /api/donations, then aggregate gift totals by campaign ID.

Major Gift and Stewardship Tagging

Apply structured tags to donor contacts ('major gift prospect', 'monthly recurring lapsed', 'thank-you call due') so fundraisers see priority work in their CRM view. POST /api/tags applies tags programmatically, and combining with impact-area assignment gives a stewardship team the queue they need without manual segmentation.

Tag every contact with a lifetime giving total over $5,000 as 'major-gift-prospect' via POST /api/tags.

Agent-Driven Fundraising Operations

A nonprofit's AI assistant uses Jentic to update Keela when a fundraiser says 'log Sarah's $500 gift to the climate campaign' or 'tag the volunteer board as monthly donors'. Jentic resolves the contact and campaign by name, picks the right endpoint, and executes the call, with the OAuth credentials staying in the vault and never appearing in chat with the assistant.

Use the Jentic search 'record a Keela donation', load the schema, and POST /api/donations for the contact, campaign, and amount specified by the fundraiser.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for keela api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/campaigns

List fundraising campaigns

GET

/api/contacts

List donor contacts

GET

/api/households

List households

GET

/api/impact_areas

List impact areas

GET

/api/sources

List campaign attribution sources

GET

/api/tags

List donor tags

GET

/api/donations

List donations

GET

/api/revenues

List revenues

GET

/api/campaigns

List fundraising campaigns

GET

/api/contacts

List donor contacts

GET

/api/households

List households

GET

/api/impact_areas

List impact areas

GET

/api/sources

List campaign attribution sources

GET

Why Jentic?

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

Credential isolation

Keela OAuth2 access tokens are held encrypted in the Jentic vault. Agents receive scoped execution tokens, so the raw bearer token and any refresh token never appear in prompts or transcripts.

Intent-based discovery

Agents search by intent (for example, 'record a Keela donation' or 'tag a major-gift donor') and Jentic returns the matching path with body schema, removing the need to read Keela's developer docs.

Time to first call

Direct Keela integration: 1-2 days for OAuth handling, contact and campaign resolution, and donation construction. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Keela API through Jentic.

Why is there no official OpenAPI spec for Keela API?

Keela does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Keela API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Keela API use?

The API uses OAuth2 access tokens. Each request includes `Authorization: Bearer {token}` where the token is issued from the Keela tenant's API settings. Through Jentic the token is held encrypted in the vault and injected at execution time so the agent never sees the raw access token.

Can I record a donation against a campaign with the Keela API?

Yes. POST /api/donations accepts a contact reference, campaign ID, amount, and source ID, and the response returns the donation ID for follow-up calls. Resolve the contact first via GET /api/contacts if you only have an email, and the campaign via GET /api/campaigns if you only have a name.

What are the rate limits for the Keela API?

Keela does not publish hard rate limits in the spec. The platform tolerates typical small-charity automation traffic (nightly syncs, real-time gift posting) and returns HTTP 429 on bursts. Cache /api/sources and /api/campaigns daily — they change rarely — to keep request volume down.

How do I tag a Keela donor through Jentic?

Run `pip install jentic` and search Jentic for 'tag a Keela donor'. Jentic returns the schema for POST /api/tags; supply the contact ID and tag name, then execute. The OAuth token is injected from the Jentic vault.

Does the Keela API distinguish donations from other revenue?

Yes. POST /api/donations records charitable gifts that need receipts; POST /api/revenues records non-donation revenue like grants, sponsorships, and earned income. Keep them on the right endpoint so tax-receipt automation does not issue receipts for non-donation revenue.

Is the Keela API included in every plan?

API access is included with Keela paid plans for nonprofits. The free or trial tier may be read-only; check the tenant plan if POST /api/donations returns 403.