Bloomerang API

Name: Bloomerang API API
Brand: Bloomerang API
Availability: InStock

★ Only Publicly Available SpecCRMContact ManagementapiKey, oauth2111 EndpointsREST

For Agents

Manage nonprofit donor records, transactions, pledges, campaigns, and communications in Bloomerang CRM through structured CRUD operations.

Quickstart

Get started with Bloomerang 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:
"create a Bloomerang constituent"

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

Capabilities

What an agent can do with Bloomerang API API.

Create and update constituent records with addresses, emails, phones, and custom fields

Record one-time donations, recurring pledges, and pledge payments against a donor

Organise giving into campaigns, appeals, and funds with their own performance summaries

Log interactions, notes, and tasks against a constituent for stewardship workflows

GET STARTED

Start building with Bloomerang API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Bloomerang API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Bloomerang API, keeping it validated and agent-ready. Bloomerang is a donor management CRM for nonprofits, and the v2 API exposes constituents, households, transactions, pledges, campaigns, appeals, funds, tributes, communications, tasks, and relationships as structured resources. It supports both private API keys for server-to-server use and OAuth 2.0 authorization-code flow with scoped roles for end-user apps. The base URL is https://api.bloomerang.co/v2 with 111 documented endpoints across donor records and fundraising operations.

Use Cases

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

★ Donation intake from a custom form

Capture donations from a nonprofit's own website or event landing page and post them into Bloomerang. The flow looks up or creates a constituent via /constituents and /constituent, then posts a transaction via /transaction with the amount, fund, campaign, and appeal references. Suitable for replacing or supplementing Bloomerang's hosted donation forms when the nonprofit needs custom branding or fields.

Look up a constituent by email via GET /constituents/search, then call POST /transaction with amount, fundId, campaignId, and appealId for a $100 gift.

Donor stewardship automation

Automate stewardship touchpoints by logging interactions and tasks against constituent records. POST /interaction records a contact (call, email, meeting), POST /note attaches an observation, and POST /task assigns a follow-up to a staff member with a due date. This supports thank-you call workflows, lapsed-donor outreach, and major gift cultivation tracking.

Call POST /interaction to log a thank-you call against constituent ID 12345, then POST /task to assign a 30-day follow-up to a staff member.

Campaign performance reporting

Build campaign performance reports by combining /campaigns, /appeals, /funds, and /transactions data. The /campaigns/refreshsummaries endpoint forces a recalculation of totals, and per-campaign and per-appeal endpoints return goal, raised amount, and donor counts. Useful for executive dashboards, board reports, and end-of-year giving snapshots.

Call GET /campaigns/refreshsummaries, then GET /campaigns and return each campaign's name, goal, and raised amount.

Household and relationship management

Maintain household groupings and constituent-to-constituent relationships for accurate acknowledgement letters and grateful giving recognition. POST /household groups members, POST /relationship links two constituents under a role (spouse, child, employer), and the relationship roles endpoints return the configurable taxonomy. This supports family giving rollups and matching-gift relationships.

Call POST /relationship to link constituent A to constituent B with role 'Spouse' and isPrimary=true.

AI agent fundraising assistant

Let an AI agent help nonprofit staff find donor records, log interactions, and post gifts on their behalf. The agent searches Jentic for the right Bloomerang operation by intent, loads the schema, and executes with the API key or OAuth token held in the Jentic vault. Suitable for development-team copilots, voice-driven gift entry, and automated stewardship reminders.

Search Jentic for 'create a Bloomerang constituent', load the schema, and execute it with first name, last name, and primary email for a new donor.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/transaction

Record a donation or pledge payment

POST

/relationship

Link two constituents under a defined role

POST

/interaction

Log a stewardship touchpoint against a constituent

GET

/campaigns

List campaigns with current totals

POST

/campaign

Create a new campaign

GET

/funds

List funds available for gift attribution

POST

/tribute

Create a tribute record for in-honor or in-memory giving

GET

/user/current

Return the authenticated user's profile

POST

/transaction

Record a donation or pledge payment

POST

/relationship

Link two constituents under a defined role

POST

/interaction

Log a stewardship touchpoint against a constituent

GET

/campaigns

List campaigns with current totals

POST

/campaign

Create a new campaign

Why though Jentic?

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

Credential isolation

Bloomerang API keys and OAuth tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access — raw X-API-KEY headers and OAuth refresh tokens never enter agent context, and OAuth scope (ViewOnly through OrgAdmin) is enforced at credential-grant time.

Intent-based discovery

Agents search by intent (e.g. 'record a donation' or 'find a constituent by email') and Jentic returns the matching Bloomerang operation across the 111 endpoints with its input schema, so the agent can call the right path without browsing the docs site.

Time to first call

Direct integration: 2-4 days for OAuth consent flow, scope handling, and donor-record schema mapping. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Blueshift

Customer engagement platform — pair when sending donor email and push campaigns based on Bloomerang gift events

Use when an agent must trigger a Blueshift campaign in response to a Bloomerang donation or pledge

Complementary

Bluetick

Email follow-up automation — pair for stewardship sequences after a gift is recorded

Use when an agent records a gift in Bloomerang and needs to start a Bluetick follow-up sequence

Complementary

BlueInk

E-signature platform — pair for pledge agreement and major gift commitment signing

Use when an agent must collect a signed pledge document tied to a Bloomerang pledge record

FAQs

Specific to using Bloomerang API API through Jentic.

Why is there no official OpenAPI spec for Bloomerang API?

Bloomerang publishes a Swagger UI page with endpoint reference but does not distribute a maintained OpenAPI 3 file. Jentic generates and maintains this spec so AI agents and developers can call the Bloomerang API via standard 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 Bloomerang API use?

Two methods are supported: a private API key passed in the X-API-KEY header for server-to-server integrations, and OAuth 2.0 authorization code flow with scopes ViewOnly, StandardEditFinancialData, Standard, and OrgAdmin for end-user applications. Through Jentic, both credential types are stored in the encrypted vault and injected at execution.

Can I record a donation through the Bloomerang API?

Yes. POST /transaction creates a transaction record with fields including amount, type (Donation, Pledge, PledgePayment, RecurringDonationPayment), accountId for the donor, and fundId, campaignId, and appealId for attribution. The response returns the new transaction's id.

What are the rate limits for the Bloomerang API?

Bloomerang enforces per-account rate limits that vary by plan, with HTTP 429 returned when exceeded. The published guidance is to stay below roughly 10 requests per second per API key; long-running batch jobs should use exponential backoff on 429 responses.

How do I look up a constituent by email through Jentic?

Search Jentic for 'find a Bloomerang constituent by email', load the schema for GET /constituents/search, and execute it with the email in the search query. Install with pip install jentic and call await client.execute(ExecutionRequest(...)). Returns matching constituent IDs you can then GET in detail.

Does Bloomerang support recurring pledge tracking?

Yes. POST /transaction with type=Pledge creates a pledge schedule, and subsequent POST /transaction with type=PledgePayment and a parentTransactionId records each instalment. The /pledges and /pledgePayments endpoints let you list and reconcile schedules.

Is the Bloomerang API free?

API access is included with a Bloomerang subscription — there is no separate API fee. Pricing is tied to the Bloomerang plan tier and the size of the constituent database, which determines available scopes (ViewOnly, Standard, OrgAdmin) for OAuth applications.