Create/retrieve constituents and record donations in Bloomerang via its REST API v2
domain: bloomerang.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
As an Administrator user in Bloomerang, go to User Settings and generate a v2.0 API key (private key for server-to-server use)
Send requests to the v2 base URL (https://api.bloomerang.co/v2) with the API key in the X-API-Key header
POST to /constituent to create a new constituent, or GET/search existing constituents to avoid duplicates before creating
POST to /transaction to record a donation, specifying the constituent ID and at least one designation (donation, pledge, pledge payment, or recurring donation/payment)
You are responsible for actually processing payment (via your own payment processor) before submitting the finished transaction data to Bloomerang — Bloomerang's API does not process payments itself
Use the GET list/search endpoints to retrieve a constituent's donation history for reconciliation
Known gotchas
Bloomerang has both a legacy REST API v1 and the current REST API v2 with different auth and endpoint shapes — new integrations should use v2
The API does not process payments; you must collect funds yourself and push the finished transaction record, unlike payment-processing APIs
Bloomerang acquired Kindful and Qgiv — if a client mentions any of those product names, confirm which underlying API/account they're actually on before assuming this is the right endpoint set
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?