Skip to main content

Fundraise Up API Endpoints

Reference for the Fundraise Up API endpoints the iPaaS.com integration calls, for firewall whitelisting, troubleshooting, and impact assessment.

See what the Fundraise Up integration can do →

Portal Info

The Fundraise Up web dashboard is available at:

https://dashboard.fundraiseup.com

API Endpoints

The Fundraise Up integration uses the Fundraise Up API, a RESTful API that provides access to donation, supporter, recurring plan and event-log data within a Fundraise Up account. The integration only reads from it.

Base URL:

[API Url]

The API Url value is configured in the iPaaS.com Subscription Settings. Its default is https://api.fundraiseup.com/v1 (the address includes https://). Fundraise Up uses the same address for live and test data.

Live or test data: every request the integration sends carries the query parameter livemode, set from the subscription's Livemode setting (true for live data, false for test data). Fundraise Up requires this parameter for API keys created after 30 January 2026.

Paging: Fundraise Up lists records newest first, up to 100 per page. The cursor ending_before returns records newer than the given ID, and starting_after returns records older than it; Fundraise Up does not accept both in one request.

Request limit: Fundraise Up accepts up to 3 requests in parallel per account, across all its API keys, live and test together. See Fundraise Up Known Limitations for the setting to use.

Table of Contents

  • Donation Endpoints

  • Supporter Endpoints

  • Recurring Plan Endpoints

  • Event Log Endpoints


Donation Endpoints

List Donations (GET)

Retrieves a page of donation records, newest first. The integration lists donations in four situations:

  • Connection check: when the integration connects, it reads one donation to confirm the API key and address work.

  • First poll on a new subscription: reads back through history to the Donation Poll Days limit, paging older with starting_after.

  • Later polls: reads the donations newer than the last one already read, paging newer with ending_before.

  • Recurring plan changes: finds a plan's latest donation by paging back through the newest donations with starting_after.

[Base URL]/donations?limit=1
[Base URL]/donations?limit=100&created[gt]={date}&starting_after={donationId}
[Base URL]/donations?limit=100&ending_before={lastReadDonationId}
[Base URL]/donations?limit=100&starting_after={donationId}

Query parameters:

Parameter

Description

limit

Page size, from 1 to 100.

ending_before

Cursor: returns donations newer than this donation ID.

starting_after

Cursor: returns donations older than this donation ID.

created[gt]

Creation-date filter. Used only on the first poll, to apply the Donation Poll Days setting; left out when that setting is 0 or blank.

livemode

Live or test data, from the Livemode setting. Sent on every request. When a donation or supporter isn't found, the integration reads it once more in the other mode, only to report FUUP-VALD-1006 if it is there.

Get a Donation by Id (GET)

Retrieves a single donation by its Fundraise Up donation ID, with its payment, supporter, campaign, designation and recurring plan details. Used for every donation transfer to iPaaS.com, whether it was started by the poll, the Fundraise Up webhook or a Manual Sync.

[Base URL]/donations/{Id}

Supporter Endpoints

Get a Supporter by Id (GET)

Retrieves a single supporter (donor) by its Fundraise Up supporter ID, with the supporter's address. Used when a donation's supporter is sent to iPaaS.com as a Customer, and for a Manual Sync of a supporter.

[Base URL]/supporters/{Id}

Recurring Plan Endpoints

Get a Recurring Plan by Id (GET)

Retrieves the current recurring plan (status, amount, currency, end date, cancellation reason) when a recurring installment is transferred, so the iPaaS.com Transaction carries the plan's current state.

[Base URL]/recurring_plans/{Id}

Event Log Endpoints

List Events (GET)

Retrieves Fundraise Up's event log, newest first. Each scheduled poll reads the events newer than the last one it processed and sends again the donations they name (refunds, status changes, edits, recurring plan changes). On its first run the poll reads only the newest event, to set its starting point. The same one-event read checks whether the API key can read Events.

[Base URL]/events?limit=1
[Base URL]/events?limit=100&ending_before={lastReadEventId}

Webhook Receiver

Fundraise Up sends donation and recurring plan events to the iPaaS.com webhook address you create in Settings > Webhooks. iPaaS.com checks the Webhook API Key in the address, then the integration reads each donation the event names by its id (see Get a Donation by Id). See Fundraise Up Installation Instructions for the address and setup steps.

Authorization Endpoint

The Fundraise Up API uses a static API key passed as an HTTP Bearer token on every request. There is no separate authorization endpoint and no token exchange:

Authorization: Bearer <API Key>

The API key is configured in the iPaaS.com Subscription Settings. See Fundraise Up Installation Instructions for how to create an API key in your Fundraise Up account and set it on the subscription.

Related Documents

Did this answer your question?