Before You Begin
Before you can install the Fundraise Up subscription, you need the following:
A Fundraise Up API Key with Read on Donations, Supporters, Recurring plans and Events, in the mode this subscription uses (live or test). One key can hold both modes; see the end of this section.
The Fundraise Up API Url, https://api.fundraiseup.com/v1. It is the same for live and test data.
A decision on Livemode: True for a production subscription that reads live donations, False for a staging or UAT subscription that reads test donations.
In iPaaS.com: a Payment Method named Other in your company (every Fundraise Up payment method arrives as Other by default), and two Products, one for donations and one for donor-covered processing fees. You enter their SKUs in the Designation and Surcharge collections before the first transfer (see Operational Configuration).
One subscription per Fundraise Up account and mode. In each iPaaS.com company, create only one Fundraise Up subscription for a given Fundraise Up account in a given mode (test or live). Two subscriptions on the same account and mode both transfer every donation into the same iPaaS.com Transaction, which can then end up with extra lines that downstream systems pick up. See Use one subscription per Fundraise Up account and mode in each iPaaS.com company in Fundraise Up Known Limitations.
Donor-covered fees. Decide how a processing fee the donor chose to cover should arrive: as its own surcharge line (setting Surcharge As Line Item = Yes) or inside the donation's single line (No). With Yes, the surcharge line needs its own product (see Operational Configuration). See A processing fee the donor covers can arrive as its own line in Fundraise Up Known Limitations. On a subscription saved before the setting existed (its Surcharge As Line Item setting has no value, which reads as off), first follow the steps in the Fundraise Up Version 1.0.3 Upgrade Guide, and turn the setting on last; otherwise the fee arrives as a second designation line.
To create an API Key in Fundraise Up
Only a Fundraise Up user with the Organization Administrator role can create and manage API keys.
Log in to your Fundraise Up account.
Click Settings in the left-side navigation.
Under the Administration section, select API keys.
Click Create API key.
Provide a descriptive name (for example, iPaaS.com - Live) and select the required permissions, then click Create API key.
The integration only reads from Fundraise Up: it retrieves donations, supporters, recurring plans and the event log. In the Live data section, enable Read access on the four data types below. (Only for a test subscription whose Livemode is False, tick the same four rows in the Test data section instead.)
Donations: Read. Access donation information.
Supporters: Read. Access supporter information.
Recurring plans: Read. The integration reads the recurring plan (status, amount, end date) when it transfers an installment. Without it, installments still transfer, but their plan fields stay as the donation reported them.
Events: Read. Each poll reads Fundraise Up's event log to pick up changes after a donation was created (refunds, failures, recurring plan changes). Without it, new donations still arrive, but refunds and recurring plan changes do not reach iPaaS.com by the poll, and the error FUUP-AUTH-1003 appears under Dashboard / Integration Monitoring / Error Logs.
Leave all other rows unchecked. The integration does not write to Fundraise Up and does not use the other rows (Designation configurations, Fundraisers, Donor Portal access links, Upgrade links, Campaigns, Designations, Designation groups or Subaccounts): no Write access and no additional Read permissions are required.
Other notes:
Fundraise Up requires at least one permission in either the Live data or Test data section.
Permissions can be changed 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.
Fundraise Up shows the new key once, in the New API key window, with a Copy button next to it.
Important: Copy the API key into a safe place (a password manager is recommended) before closing this window. Fundraise Up shows the key only once and you cannot retrieve it later. If you lose it, remove the key and repeat the previous two steps to create a new one.
The new API key now appears in the list of API keys. The Access level column shows whether the key has Live data or Test data permissions.
To edit permissions or remove an existing key, click the three-dot menu on the right side of the entry and select Edit key or Remove.
A single Fundraise Up API key can grant permissions on Live data, Test data, or both: the key itself is not bound to one mode. The same key can therefore serve a staging iPaaS.com subscription (reading test data) and a production iPaaS.com subscription (reading live data), provided you grant the relevant Read permissions in both sections. For a production (live) subscription, we recommend a key with Live data permissions only. The Livemode setting already makes every request read live data, but a live-only key also means a misconfigured setting cannot read test data, and the reverse for a test-only key on a staging subscription.
Installation Instructions for Integration Setup
Go to Subscriptions and click Search Certified Integration Marketplace and Subscribe.
Click the Fundraise Up integration tile.
Click the Subscribe button.
Enter a name for the subscription. It can be any relevant name that is unique within the company where this subscription is created.
Format: Fundraise Up - [Environment/Purpose]
Example: Fundraise Up - Production
Select a version from the Versions dropdown. Choose the latest version unless your MiSP has asked you to use another.
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.
Enter the API Url for the Fundraise Up API: https://api.fundraiseup.com/v1. The field starts empty.
This is the same URL for live and test data; the API key and the Livemode setting decide which data is read, not the URL.
The API Url is required: iPaaS.com does not save the subscription with an empty API Url.
Enter the API Key you created in Before You Begin. This is the secret value that authenticates iPaaS.com to your Fundraise Up account.
Select Livemode from the dropdown: True for live data or False for test data, to match the mode your API key was made in. Check the value before saving.
True: production subscription, reading live donations.
False: staging or UAT subscription, reading test donations.
Livemode is a True/False setting: iPaaS.com saves only True or False for it (in any letter case) and refuses any other value when you save the subscription.
The API key must have Read permission on the matching data 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.
Warning: set Livemode once, to match your API key, before the first transfer.
If Livemode doesn't match the mode your API key was made in, donations don't transfer. Each one stops with FUUP-VALD-1006, which names the Livemode value to set. Make sure Livemode matches the key's mode (Live data or Test data) before the first transfer. A key that reads both Live and Test data also reaches donations made in the other mode, such as test donations on a live subscription, and each of those stops with FUUP-VALD-1006 to dismiss. To avoid that, give a production subscription a key with Read on Live data only.
Don't change Livemode later. A subscription keeps its poll positions and its links between Fundraise Up records and iPaaS.com records for the mode it has been reading, and Fundraise Up's live and test data are separate. Changing Livemode on a subscription that has already transferred donations would mix records from two separate sets of Fundraise Up data under one subscription. Use a separate iPaaS.com subscription for each mode. If you think you need to change Livemode on an existing subscription, consult your MiSP (Managed Integration Service Provider) first. See Livemode is set once for the life of a subscription in Fundraise Up Known Limitations.
Enter Donation Poll Days (optional). It bounds how far back the first donation poll on this new subscription looks: donations older than this many days are left out of the first run. The setting is read only by that first poll (while the subscription has no saved poll position); after the first poll it is not read again, so a later change (even an invalid value) has no effect.
The field starts empty, and a blank value makes the first poll read every donation. Enter the number of days you want (for example
7) before the first poll runs.Blank or
0imports every donation. A negative number or text (for example-5or7 days) stops the first poll with FUUP-VALD-1004 until it is corrected.Raise this value (for example
365for a full year or1825for five years) before the first scheduled poll runs when you need a larger historical import. There is no separate Initialize Data step. See Fundraise Up Connections and Settings for the full description.
Enter Surcharge As Line Item.
Yesputs a processing fee the donor chose to cover on its own surcharge line;Nokeeps it inside the donation's single line, at the gross amount. See Before You Begin and Fundraise Up Connections and Settings.The field starts empty; an empty value works like
No.Any value other than Yes or No (True/False, 1/0 and On/Off are also accepted) stops each donation transfer with FUUP-VALD-1002. iPaaS.com does not save a blank value for this setting (the previous value is kept).
Check the throttle and concurrency settings. They are standard iPaaS.com subscription settings, shown on every subscription, and the subscription form fills them in:
API Throttle Limit: Default:
500. The maximum number of API calls per throttle window.API Throttle Seconds: Default:
60. The length of each throttle window, in seconds.API Throttle Limit (to iPaaS.com): Default:
500. The maximum number of inbound (to iPaaS.com) API calls per throttle window.API Throttle Seconds (to iPaaS.com): Default:
60. The length of each inbound throttle window, in seconds.Concurrent Connections: Default:
2. The maximum number of simultaneous connections iPaaS.com opens for this subscription. Keep it at1or2; never above2. See Important Notes under Authentication Configuration.Concurrent Batch Executions: Default:
10. The number of batch operations that can run at once. This integration does not run batch operations, so the value has no effect on it.
NOTE: The throttle and concurrency settings control the frequency and volume of data movement. For Fundraise Up, the setting that matters is Concurrent Connections; see Subscription Configuration - Edit for the general description of these settings.
Click Apply to save the settings.
Authentication Configuration
API Key
Credential Name: API Key
Location: Fundraise Up dashboard, Settings > API keys (see To create an API Key in Fundraise Up)
Description: The secret key that authenticates iPaaS.com to your Fundraise Up account. The integration sends it with every request as a bearer token. There is no OAuth sign-in and no token refresh.
The API key does not expire: it stays valid until you remove it from the Fundraise Up API keys page. To rotate a key, create a new one, enter it in the iPaaS.com subscription's API Key setting, save, and then remove the old key in Fundraise Up.
Important Notes
Fundraise Up rate limit. Fundraise Up limits each account to 3 API requests in parallel, across all endpoints and all API keys of the account, test or live. Additional requests are refused with HTTP 429 and the code concurrent_requests_limit_exceeded. Fundraise Up advises keeping an integration single-threaded.
What this means for your subscription configuration:
Set Concurrent Connections to
1(single-threaded, as Fundraise Up advises) or2. Do not exceed2. With a higher value, Fundraise Up refuses some requests as too many at once, and those transfers are retried after about 60 seconds with FUUP-EXTN-1005. Concurrent Connections is the setting for this limit: API Throttle Limit and API Throttle Seconds limit the number of calls per time window and cannot prevent parallel requests, so leave them at their defaults.If you run several iPaaS.com subscriptions against the same Fundraise Up account (for example a staging subscription on test data and a production subscription on live data), the sum of their Concurrent Connections values must stay at or below
3. A parent account and its subaccounts are counted separately.
For Fundraise Up's own description of the API and its rate limit, see:
API rate limits: https://api.fundraiseup.com/v1/docs/#/#rate-limits
Full API reference: https://api.fundraiseup.com/v1/docs/#/
Operational Configuration
Do these steps after you subscribe; they are required. Three things don't come with the subscription. Without them no donation reaches iPaaS.com. A fourth, the Fundraise Up webhook, is recommended: with it, donations arrive within seconds instead of on the poll schedule (see Create the Fundraise Up webhook below).
Create the donation and surcharge products (before the first transfer)
iPaaS.com refuses a transaction line whose SKU isn't one of the company's existing products, so both line collections need an existing product before the first poll runs or the first webhook arrives:
Create two products in iPaaS.com: one for donations (for example SKU General Giving) and one for donor-covered processing fees (for example SKU Surcharge). If a system downstream receives transaction lines from iPaaS.com, create the same SKUs there too.
In the Add/Update Fundraise Up Designation TO iPaaS.com collection, set the Static Sku mapping to the donation product's SKU. It ships with a placeholder value that names no product.
In the Add/Update Fundraise Up Surcharge TO iPaaS.com collection, set the Static Sku mapping to the surcharge product's SKU. It also ships with a placeholder value. Set it even if you start with Surcharge As Line Item =
No, so that turning the setting on later does not stop donations.
Until both SKUs name existing products, every donation that has that line is refused with NFND-1003 - Product Id: … does not exist or can not be found.
Check the Payment Method Other
The template's payment method translation maps every Fundraise Up payment method to the iPaaS.com Payment Method Other. Check that your company has a Payment Method named Other, and create it if not. If you remap methods in the translation (for example credit_card to Credit Card), each target method must exist too. The raw Fundraise Up method is always kept on the Payment's Description.
Schedule the donation poll (the backstop)
The poll is required, even when you create the Fundraise Up webhook below. It picks up any donation or change the webhook missed (for example while Fundraise Up had the webhook switched off) and it keeps working with no webhook at all. It doesn't send again a new donation the webhook already brought. It does send every change again, even one the webhook already brought; that repeat updates the same Transaction with the same values. Subscribing creates no schedule. Under Dashboard / Integration Monitoring / Events, add an event of type Webhook Poll Request (the platform's name for a scheduled poll):
Field | Value |
System | this Fundraise Up subscription |
Scope | transaction/poll |
Schedule | for example 0 0/15 * * * ? (a cron expression, the format the Events page takes: every 15 minutes, on the quarter hour). With the Fundraise Up webhook on, the poll can run less often, for example once a day. |
Each run reads every donation created since the last one it read, and every change Fundraise Up recorded since the last run (refunds, disputes, recurring plan changes). The very first run reads only the donations created in the last Donation Poll Days days (step 10), and starts reading changes from the newest one at that moment, without replaying older changes. There is no separate Initialize Data step. To learn which changes are picked up and how, see Changes after a donation is created arrive by webhook or poll in Fundraise Up Known Limitations.
How to tell it works: after the next scheduled time, the event's last run shows COMPLETE - Sent hook to iPaaS API, and no Fundraise Up error appears under Dashboard / Integration Monitoring / Error Logs.
Create the Fundraise Up webhook (recommended)
A webhook makes Fundraise Up tell iPaaS.com about each new donation and each change as it happens; a delivery reaches iPaaS.com within seconds. The webhook is configured manually in Fundraise Up: Fundraise Up offers no way to create a webhook from outside its dashboard, so iPaaS.com can't create it for you. You create it once, by hand, in Fundraise Up for each iPaaS.com subscription. The integration fully supports webhooks once the webhook exists; there is nothing to turn on in iPaaS.com, and the integration's webhook scopes need no activation.
You need your subscription's Webhook API Key. iPaaS.com generates it when the subscription is saved, and it tells iPaaS.com which subscription a webhook is for. To find it, go to Subscriptions, open your Fundraise Up subscription's settings, and scroll to the Webhook API Key field at the bottom of the page. The key is masked; click the copy icon at the end of the field to copy it. This is not your Fundraise Up API key.
Build the webhook address. It has this form:
https://api.ipaas.com/hookapi/v2/dynamic/fundraiseup?AuthToken={your subscription's URL-encoded Webhook API Key}
On iPaaS.com staging, the host is stagingapi.ipaas.com instead of api.ipaas.com. The address is the same whether the subscription's Livemode is True or False.
Before you paste the key in, URL-encode it: replace every + with %2B, every / with %2F, and every = with %3D. Leave everything else as it is.
Treat the finished address like a password: anyone who has it can send data to your subscription.
Sign in to your Fundraise Up dashboard as an Organization Administrator.
Go to Settings > Webhooks and click Create webhook.
Give it a name you will recognize, for example iPaaS.com.
Paste the address from step 1 as the endpoint URL.
Tick these events:
Under Donations: Donation successful, Donation updated and Donation refunded.
Under Recurring plans: all five events (Recurring plan activated, Recurring plan scheduled, Recurring plan canceled, Recurring plan payment terms updated and Recurring plan supporter preferences updated).
Leave Donation created unticked. The integration accepts it and does nothing with it: a new donation's Transaction is created by Donation successful. If you tick Donation created anyway, no harm is done; it just shows as one extra delivery.
Every other donation event you tick updates the donation in iPaaS.com (a refund sets the Transaction and its Payment to Refunded), and every recurring plan event sends the plan's latest donation again with the plan's current details.
Donation scheduled is optional. Fundraise Up sends it for a donation set for a future date that hasn't been paid yet. You don't need it: the next poll brings that donation in as Pending, and Donation successful updates it once it is paid. Ticking it does no harm; the donation just comes in sooner.
Leave the Tribute and Supporter events (and any other events) unticked. The integration accepts them and runs nothing.
Click Create. Fundraise Up then shows a signing secret once. You don't need it: iPaaS.com checks the Webhook API Key in the address instead. You can close the dialog without saving it.
How to tell it works: after the next successful donation in Fundraise Up, its Transaction appears in iPaaS.com within seconds, without waiting for the poll. Webhooks work for test-mode donations too, so a staging subscription can be checked with a test donation. In Fundraise Up, Settings > Webhooks shows each delivery and whether it succeeded. iPaaS.com refuses a delivery whose address has a wrong or missing Webhook API Key, and nothing is transferred; if deliveries fail, check the Webhook API Key in the address (step 1). If an endpoint goes 48 hours without a successful delivery, Fundraise Up switches the webhook off; fix the address, then switch it back on there. Until it is back on, donations still arrive on the poll.
Post-Installation Verification
After completing the installation, perform these tests to verify the integration is working correctly.
Connection Test
Make sure the subscription is saved with the API Url, API Key and Livemode values from the steps above.
Run a Manual Sync of one Fundraise Up donation by its donation id (for example a test donation). The integration checks the connection to Fundraise Up at the start of every transfer.
Check Dashboard / Integration Monitoring / Error Logs. FUUP-AUTH-1002 means Fundraise Up refused the API key: paste an active key and save. FUUP-VALD-1006 means Livemode doesn't match the key's mode. Unable to connect to subscription with no other detail means the API Key is empty or Livemode holds an unrecognised value. Correct the setting, save, and run the Manual Sync again.
Check that the donation appears in iPaaS.com as a Transaction.
Data Sync Test
Create or locate a test donation in Fundraise Up, then run a Manual Sync of it (or wait a few seconds for the webhook, or for the next scheduled poll).
Verify the donation appears in iPaaS.com as a Transaction with its Payment and its designation line (plus a surcharge line when the donor covered the fee and Surcharge As Line Item is
Yes).Verify the donor appears as a Customer, with an address when the donor gave one, and that the Transaction is linked to that Customer.
Functionality Test
Run a Manual Sync of the same test donation again.
Confirm the existing Transaction is updated and no second Transaction or extra line is created.
Review Dashboard / Integration Monitoring / Error Logs for any errors. An error from a Fundraise Up call includes Fundraise Up's Request-Id; quote it when you contact your MiSP or support.
Support and Troubleshooting
Click the Help button on any iPaaS.com page to contact Support or to search our documentation.
Additional resources include:
iPaaS.com Documentation: https://support.ipaas.com/en/articles/10280417-api-introduction
iPaaS.com Support Portal: https://support.ipaas.com/en/
iPaaS.com Contact Information: https://ipaas.com/contact-us/
Fundraise Up-specific resources:
Fundraise Up API Documentation: https://api.fundraiseup.com/v1/docs/#/
Fundraise Up Support Portal: https://fundraiseup.com/support/
Common issues
Symptom | Likely cause | Resolution |
Every donation, or every donation with a covered fee, fails with NFND-1003 - Product Id: … does not exist or can not be found | The Sku in the Designation or Surcharge collection still holds its placeholder, or names a product that doesn't exist in iPaaS.com. | Create the product and set the collection's Static Sku mapping to its SKU (see Create the donation and surcharge products), then re-send the failed donations. |
Each donation transfer stops with FUUP-VALD-1002 | Surcharge As Line Item holds a value other than Yes or No. | Set it to |
The first poll stops with FUUP-VALD-1004 | Donation Poll Days is negative or not a whole number. | Enter a whole number of days, or |
No donations arrive | No Webhook Poll Request event is scheduled, and no Fundraise Up webhook is set up. | Schedule the poll (see Schedule the donation poll) and, optionally, create the webhook. |
Refunds and recurring plan changes don't arrive by the poll, and FUUP-AUTH-1003 appears | The API key has no Events: Read permission in the mode Livemode selects. | Edit the key in Fundraise Up and tick Events: Read. |
A donation fails with FUUP-AUTH-1002 | Fundraise Up refused the API key: it is wrong, revoked, or has no Read on Donations in the mode Livemode selects. | Paste an active key into API Key and check the API Url is https://api.fundraiseup.com/v1. Save, and re-send the donation. |
A donation fails with Unable to connect to subscription and no other detail | The API Key is empty, or Livemode holds a value other than True or False. | Fill in the API Key, set Livemode to True or False, save, and re-send the donation. |
Donations stop with FUUP-VALD-1006 | Livemode doesn't match the mode (Live data or Test data) your API key was made in, or the donation was made in the other mode. | Use an API key made in the mode Livemode selects. If this subscription has not transferred any donations yet, you can instead correct Livemode (see Livemode is set once for the life of a subscription in Fundraise Up Known Limitations). Save, and re-send the donations. If Livemode is right and the donation was made in the other mode, dismiss the error. |
Webhook deliveries fail in Fundraise Up's Settings > Webhooks | The Webhook API Key in the webhook address is wrong, missing or not URL-encoded. | Rebuild the address from the subscription's Webhook API Key (see Create the Fundraise Up webhook, step 1) and update the webhook in Fundraise Up. |
Subscription Settings Reference
Field | Required | Default Value | Description |
Name | Yes | None | Unique name for this subscription within the company. |
Versions | No | None | The Fundraise Up integration version, chosen from the dropdown. |
Create Default Mappings | No | Checked | Creates the standard mapping collections and translations. |
API Url | Yes | None (the field starts empty); enter https://api.fundraiseup.com/v1 | The Fundraise Up API address, the same for live and test data. |
API Key | Yes | None | The Fundraise Up API key, with Read on Donations, Supporters, Recurring plans and Events in the mode Livemode selects. |
Livemode | Yes | None (--select--); select True for live data or False for test data, to match the mode your API key was made in | True reads live data; False reads test data. A Livemode that doesn't match the key's mode stops each donation with FUUP-VALD-1006. |
Donation Poll Days | No | None (blank reads every donation on the first poll) | How many days back the first donation poll reads. Blank or |
Surcharge As Line Item | No | None (blank works like |
|
API Throttle Limit | Yes |
| Maximum number of API calls per throttle window. |
API Throttle Seconds | Yes |
| Length of each throttle window, in seconds. |
API Throttle Limit (to iPaaS.com) | Yes |
| Maximum number of inbound API calls per throttle window. |
API Throttle Seconds (to iPaaS.com) | Yes |
| Length of each inbound throttle window, in seconds. |
Concurrent Connections | Yes |
| Simultaneous connections for this subscription. Keep at |
Concurrent Batch Executions | No |
| Simultaneous batch operations. Not used by this integration. |













