Skip to main content

Fundraise Up Installation Instructions

Fundraise Up Installation Instructions

Before you can install the Fundraise Up subscription, you need to obtain the following from your Fundraise Up account:

  • API Key (one for live data and one for test data)

  • API URL (the same URL is used for both environments: https://api.fundraiseup.com/v1)

  • A decision on Livemode — set to True for a Production subscription and False for a Staging/UAT subscription

To create an API Key in Fundraise Up

  1. Log in to your Fundraise Up account.

  2. Click Settings in the left-side navigation.

    Fundraise Up dashboard left navigation with the Settings menu item.

  3. Under the Administration section, select API keys.

    Fundraise Up Settings left menu showing the Administration section with the API keys entry highlighted.

  4. Click Create API Key.

    Fundraise Up API keys page with the Create API Key button.

  5. Provide a descriptive name (for example, iPaaS — Live or iPaaS — Test) and select the required permissions, then click Create API Key.

    The integration is read-only — it only retrieves donations and supporters from Fundraise Up. For each key, enable Read access on the two data types below, in either the Live data section (for a production-mode key) or the Test data section (for a test-mode key):

    • Donations — Read. Access donation information.

    • Supporters — Read. Access supporter information.

    Leave all other rows unchecked. The integration does not write to Fundraise Up and does not call the Recurring plans, Designation configurations, Fundraisers, Events, Donor Portal access links, or Upgrade links endpoints — no Write access and no additional Read scopes are required.

    Create API key dialog showing the Name field plus the Live data and Test data permission tables; Read access on Donations and Supporters is the required minimum for the iPaaS integration.

    Other notes:

    • Fundraise Up requires at least one permission to be selected in either the Live data or Test data section before the Create API Key button activates.

    • Permissions can be modified later from the API keys list page — click the three-dot menu next to the key and select Edit key.

    • For the full reference of every Fundraise Up permission and what it grants, see How to get an API key in Fundraise Up's API documentation.

  6. The New API Key window opens with the generated key value.

    New API key dialog showing the generated key value and the Copy affordance.

    Important: Copy the API key into a safe place (a password manager is recommended) before closing this window. The full key value will not be displayed again. If you lose it, you must remove the key and repeat the previous two steps to generate a new one.

  7. The new API key now appears in the list of available API keys.

    Fundraise Up API keys list page showing the newly-created key.

  8. To edit permissions or remove an existing key, click the three-dots menu on the right side of the entry and select Edit key or Remove.

    API key row three-dots menu showing the Edit key and Remove options.

A single Fundraise Up API key can grant permissions on Live data, Test data, or both — the key itself is not bound to a single environment. The same key can therefore serve a staging iPaaS subscription (operating against test data) and a production iPaaS subscription (operating against live data), provided you grant the relevant Read permissions on both sections. Most subscribers keep one key per iPaaS subscription with permissions scoped to that subscription's data tier; a shared cross-environment key works equally well.

Installation Instructions for Integration Setup

  1. Go to Subscriptions and click Search Certified Integration Marketplace and Subscribe.

    iPaaS.com Subscriptions page with the Search Certified Integration Marketplace and Subscribe button highlighted.

  2. Click the Fundraise Up integration tile.

    iPaaS.com integration marketplace showing the Fundraise Up integration tile.

  3. Click the Subscribe button.

    Fundraise Up integration detail page with the Subscribe button.

  4. Enter a name for the subscription. It can be set to any relevant and unique subscription name within the company where this subscription is created.

    • Format: Fundraise Up - [Environment/Purpose]

    • Example: Fundraise Up - Production

  5. Select Create Default Mappings (recommended). If you don't want to create default mappings and prefer to create all mappings yourself, un-check this box.

    New Subscription form showing the Name field, version selector, and Create Default Mappings checkbox.

  6. Enter the API Url for the Fundraise Up API.

    • Default value: https://api.fundraiseup.com/v1

    • This is the same URL for both test and production data; environment selection is controlled by the API key and the Livemode setting, not the URL.

  7. Enter the API Key you retrieved in Before You Begin. This is the secret value that authenticates iPaaS.com to your Fundraise Up account.

  8. Set Livemode based on which Fundraise Up data tier this subscription should operate against:

    • True — production subscription, polling live donations.

    • False — staging or UAT subscription, polling test donations.

    The supplied API key must have Read permission on the matching data tier in Fundraise Up (see step 5 of To create an API Key in Fundraise Up). A key with permissions on both Live and Test data can serve either Livemode value.

    Subscription settings page showing the Livemode toggle.

    DESTRUCTIVE SETTING — READ BEFORE CHANGING

    Livemode looks like a simple toggle, but flipping it on a subscription that has already imported donations causes data corruption that is hard to detect and harder to recover from. iPaaS.com has no built-in staging-to-production-and-back cleanup on an existing subscription; the Livemode dropdown does not reset external-id links or the poll watermark when its value changes. Use separate iPaaS.com subscriptions per environment and flag records (e.g., a Static field mapping or a tag on each Transaction) so downstream live destination integrations can filter test transactions out by content rather than relying on subscription-level state.

    Fundraise Up's Live and Test environments are isolated namespaces. The same donation id can exist in both, referring to completely different records. When Livemode is changed mid-life:

    • The external-id records linking iPaaS Transactions to Fundraise Up donation ids remain in place, but the integration now polls a different namespace.

    • The poll watermark (Poll_Donations_LastId) still references the previous environment's most recent donation id, which may not exist in the new environment — leading to duplicate Transaction creation, updates against the wrong Transactions, or silent stalls.

    • In the worst case, new donations from the swapped environment land as Updates against existing iPaaS Transactions that were originally created from the other environment, silently corrupting historical data.

    If you are unsure whether your situation calls for a Livemode change, do not change the setting. Consult your MiSP (Managed Integration Service Provider) or implementation partner before proceeding — the cost of a wrong flip is significantly higher than the cost of a short consultation. Once corruption sets in, recovery typically requires deleting and rebuilding the affected iPaaS records.

  9. Enter Donation Poll Days (optional). Bounds how far back the initial donation poll on this new subscription will look — donations older than this many days are excluded from the first run. After the first poll establishes a watermark, the setting no longer applies. Default is 7 days. Raise this value (e.g., 365 for a full year, 1825 for five years) before triggering Initialize Data when a larger historical backfill is required. See Fundraise Up Connections and Settings for the full description and recommended values.

    • Default value: 7

  10. Enter the API Throttle Limit. This setting prevents any single integration or user from overwhelming the system with too many requests.

    • Recommended value: 0 (Unlimited) for initial setup.

  11. Enter the API Throttle Seconds. This defines the time window during which the API Throttle Limit is measured.

    • Default value: 0 (Unlimited)

  12. Enter the number of Concurrent Connections. This specifies the maximum number of simultaneous API connections that iPaaS.com can process for this subscription.

    • Default value: 1

    • Range: 1

  13. Enter the number of Concurrent Batch Executions. This specifies the maximum number of simultaneous batch executions that can process for the Fundraise Up integration at one time. (Batch execution is not currently exercised by this integration.)

    • Default value: 10

    • Range: 1–10

  14. Click Apply to save the settings.

Authentication Configuration

Fundraise Up uses a static API key sent as an HTTP Authorization: Bearer <key> header. There is no OAuth handshake and no token refresh.

The API key does not expire automatically — it remains valid until you manually remove it from the Fundraise Up API Keys settings page. To rotate a key, create a new one, update the iPaaS subscription's API Key preset, save, and then remove the old key from Fundraise Up.

Important Notes

Fundraise Up rate limit. Fundraise Up enforces a concurrency-based API rate limit: a Fundraise Up account can have at most 3 parallel API requests in flight at any moment, across all endpoints and all API keys (live and test combined). Excess requests are rejected with HTTP 429 and the error code concurrent_requests_limit_exceeded.

What this means for your subscription configuration:

  • In the iPaaS.com subscription settings, leave Concurrent Connections at 1 (the default — single-threaded, matches Fundraise Up's published guidance) or set it to 2. Do not exceed 2. Concurrent Connections is the correct preset for this constraint — the API Throttle Limit / API Throttle Seconds presets enforce a per-second rate and cannot defend against a concurrency limit; leave those at their defaults.

  • If you operate multiple iPaaS.com subscriptions against the same Fundraise Up account (e.g., separate staging and production subscriptions sharing one account's test-mode and live-mode keys), the sum of their Concurrent Connections values must stay at or below 3.

For authoritative details on the API and its rate limit, see:

Post-Installation Verification

After completing the installation, perform these tests to verify the integration is working correctly.

  1. Data Sync Test — Create or locate a test donation in Fundraise Up, then trigger a manual sync (or wait for the next scheduled poll). Verify the donation appears in iPaaS.com as a Transaction record with the expected Supporter, Supporter Address, and Payment children populated.

  2. Functionality Test — Update the test donation in Fundraise Up (for example, change a custom field) and confirm the change propagates to iPaaS.com on the next poll. Review integration logs in iPaaS.com for any errors. Every error log entry includes the Request-Id response header from Fundraise Up — supply this id to Fundraise Up Support if you need to escalate a transaction-level issue.

Support and Troubleshooting

Click the Help button on any iPaaS.com page to contact Support or to search our documentation.

Additional resources include:

Fundraise Up-specific resources:

Related Documents

Related Articles
Fundraise Up API Endpoints
Fundraise Up Connections and Settings
Fundraise Up Known Limitations
Fundraise Up to iPaaS.com Donation Mapping Documentation
Fundraise Up Error Messages
Did this answer your question?