Export donation records from Fundraise Up and keep external systems in sync
domain: fundraiseup.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an API key from your Fundraise Up dashboard and send it as a Bearer token to the API base URL https://api.fundraiseup.com
GET /v1/donations to list/export donation records, using pagination and filters (e.g. date range) to pull incremental updates
GET /v1/recurring-plans, /v1/supporters, and /v1/events for the other exportable resource types
If you need to create/update a donation collected offline, POST to /v1/donations — note that updates are only permitted within 24 hours of creation and only for API-created donations
Since Fundraise Up does not support outbound webhooks to arbitrary external URLs, use their Zapier integration (or scheduled polling of the export endpoints) to get near-real-time sync instead
Only credit card is supported as a payment method when creating donations through the API
Known gotchas
Fundraise Up explicitly does not support direct webhooks to your own server — plan on polling the export endpoints or using Zapier as the event-driven bridge instead
Donation/recurring-plan updates via the API are time-boxed to 24 hours after creation and only apply to records that originated via the API, not to donations made through the on-site widget
No bulk-update endpoint exists — every create/update is one object per request, so large syncs need request batching/rate-limit handling on your side
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?