Overview
This article lists the errors the iPaaS.com Fundraise Up integration can record, grouped by flow. The integration brings Fundraise Up donations, and each donor's supporter record, TO iPaaS.com through the Fundraise Up webhook and a scheduled poll; it never writes to Fundraise Up. Each error carries a stable code (for example FUUP-EXTN-1001) that you can find on this page with Ctrl+F, followed by the message, what causes it and how to resolve it. Errors appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs, each as the code, the message and a link to this article. The exception is a setting the integration checks while it connects to Fundraise Up (FUUP-AUTH-1001 and FUUP-VALD-1003): Error Logs show it only as "Unable to process transfer. Reason: Unable to connect to subscription with id …", without its code or message. A key Fundraise Up refuses (FUUP-AUTH-1002) shows with its code on the transfer it stopped. Errors raised by iPaaS.com itself carry two-part codes instead, for example NFND-1003 ("Product Id: … does not exist or can not be found") when the Sku of a donation line doesn't name an existing iPaaS.com product, or names no product at all because the line's Sku mapping was removed: create the product, or restore the Sku mapping, then re-send the donation.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Some resolutions refer to your Managed Integration Service Provider (MiSP): the partner who owns your integration's mappings, connection settings and credentials, and data reconciliation. When an error needs investigation rather than a fix you can make yourself, give the full message, including any Fundraise Up Request-Id, to your MiSP first; they can take it to iPaaS.com Support or to Fundraise Up.
Supported Flows
Connection and Authentication
All Flows (Fundraise Up API errors)
Donation Poll (TO iPaaS.com)
Donation Webhook (TO iPaaS.com)
Donation and Supporter Transfer (TO iPaaS.com)
Unsupported Collections and Manual Syncs
Error Collection
Connection and Authentication
A required connection setting is missing
FUUP-AUTH-1001 - Missing Setting: API Key is missing
FUUP-AUTH-1001 - Missing Setting: API Url is missing
Description: The integration could not connect because a required subscription setting is empty. No call to Fundraise Up is made. iPaaS.com refuses to save a subscription with an empty API Url, so through the subscription settings this concerns the API Key. This message is not shown in the error log: the failed transfer shows only "Unable to process transfer. Reason: Unable to connect to subscription with id …".
Resolution: That message with no other detail means a connection setting is missing or invalid. Open the subscription settings, paste an active Fundraise Up key into API Key, and check that Livemode is True or False. Save the subscription, then re-send the donations that failed, from the error log or with a Manual Sync of each donation id. The poll doesn't move its position when it can't connect, so the next poll after the fix reads the new donations.
The connection could not be validated
FUUP-AUTH-1002 - {one of the two messages below}
Messages:
Fundraise Up refused the API key (HTTP 401: {message} (code: {code})). Paste an active key with Read on Donations, Supporters, Recurring plans and Events into the API Key setting, check Livemode matches its mode, and save the subscription.
Fundraise Up answered the connection check with HTTP {status} ({message} (code: {code})). Check the API Url, API Key and Livemode settings and save the subscription.
Description: The integration checked the connection against Fundraise Up (a small read of donations) and Fundraise Up refused it. The transfer stops before anything is read, and the error log shows this code on that transfer: "Unable to process transfer. Reason: FUUP-AUTH-1002 - …". The most common causes: Fundraise Up answered HTTP 401 (the API Key is wrong, revoked or missing) or HTTP 403 (the key has no Read permission on Donations in the mode Livemode selects). When Fundraise Up is busy (HTTP 429), has a temporary error or doesn't answer the check, the transfer goes on, and its own request reports the condition with FUUP-EXTN-1005, FUUP-EXTN-1004 or FUUP-EXTN-1002.
Resolution: Open the subscription settings and check the API Key (an active Fundraise Up key with Read on Donations, Supporters, Recurring plans and Events, pasted whole), the API Url (Fundraise Up's API address, the default) and Livemode (matching the mode the key was made in, Live or Test). Paste a new key if needed and save the subscription. There is no authorization step to repeat: the key is the only credential. Then re-send the donations that failed, from the error log or with a Manual Sync of each donation id. If it persists, your MiSP can review the connection and the key.
The Livemode setting has an unrecognised value
FUUP-VALD-1003 - The subscription setting "Livemode" is "{value}". Set it to True for live data or False for test data, to match your API key, and save the subscription.
Description: Livemode decides whether the subscription reads live or test data in Fundraise Up. It takes True (live) or False (test), the only values iPaaS.com saves for it; blank means live, the default. Any other value stops the connection rather than guessing which data to read. This message is not shown in the error log: the failed transfer shows only "Unable to process transfer. Reason: Unable to connect to subscription with id …".
Note: iPaaS.com saves only True or False for Livemode, so this error normally can't occur; it remains as a safeguard.
Note: A Livemode value that doesn't match the mode the API key was made in is a different error: see FUUP-VALD-1006 below.
Resolution: That message with no other detail means the connection check failed. Open the subscription settings and check Livemode (True for live, False for test, matching the mode the key was made in), the API Key (active and pasted whole) and the API Url. Save the subscription, then re-send the donations that failed, from the error log or with a Manual Sync of each donation id. Don't switch an existing subscription between live and test: see "Livemode is set once for the life of a subscription" in Fundraise Up Known Limitations.
Livemode doesn't match the record's mode
FUUP-VALD-1006 - {Donation or Supporter} {id} is a {test-mode / live-mode} record in Fundraise Up, but this subscription's Livemode setting is {True / False}, so nothing was transferred. Set Livemode to {False / True} if this subscription's API key is a {test-mode / live-mode} key (Livemode must match the key's mode), save the subscription, and re-send the donation.
Description: The integration read the donation (or supporter) in the mode Livemode selects and Fundraise Up didn't find it, so it looked once in the other mode and found it there. Usually Livemode is set the wrong way for the API key, for example True with a key made for test data. The transfer stops with this error instead of transferring nothing. With a key that reads both live and test data, a donation made in the other mode on purpose (for example a test donation on a live subscription) also stops with this error.
Resolution: Set Livemode to match the API key's mode (False for a key made for test data, True for a key made for live data) and save the subscription. Then re-send the donations that failed, from the error log or with a Manual Sync of each donation id. If Livemode is right and the record was made in the other mode, dismiss the error: the record doesn't belong in this subscription. To avoid these on a production subscription, give it a key with Read on Live data only. Don't switch an existing subscription between live and test: see "Livemode is set once for the life of a subscription" in Fundraise Up Known Limitations.
All Flows (Fundraise Up API errors)
Fundraise Up rejected the request
FUUP-EXTN-1001 - Error calling Fundraise Up to {action}: {message} (code: {code}) (HTTP {status}) — Request-Id: {requestId}. Check the API Key setting and that the key has Read on Donations, Supporters, Recurring plans and Events in Fundraise Up, then re-send the donation.
FUUP-EXTN-1001 - Error calling Fundraise Up to {action}: {message} (code: {code}) (HTTP {status}) — Request-Id: {requestId}. Re-send the donation; if it repeats, give this message, with its Request-Id, to your MiSP, who can take it to iPaaS.com Support.
Description: After the connection was validated, Fundraise Up returned an error to a request made while polling or transferring a donation. The first message follows HTTP 401 or 403; the second follows any other status. Each names what the integration was doing (for example, read donation followed by the donation id) and carries Fundraise Up's message and code, or a short excerpt of the response, the HTTP status and Fundraise Up's Request-Id. (A key Fundraise Up rejects when the connection is made shows as FUUP-AUTH-1002 instead.) A 404 (not found) on a donation is not an error: nothing transfers and nothing is logged. The most common conditions are below.
Common causes and resolutions:
Missing Supporters permission: "Permission denied. (code: forbidden) (HTTP 403)" on a supporter read. The key can read donations but not supporters, so a new donor's donation can't be transferred. In the Fundraise Up Dashboard, under Settings > API keys, give the key Read on Supporters in the mode Livemode selects (or create a new key with Read on Donations, Supporters, Recurring plans and Events, paste it into the subscription, save, then delete the old key). Then re-send the donation.
Revoked API key: "No valid token is provided. (code: unauthorized) (HTTP 401)". The key was revoked after the connection was made. Copy a currently active key into the subscription and save. Then re-send the donations that failed, from the error log or with a Manual Sync of each donation id.
Request Fundraise Up refused as invalid (HTTP 400): Fundraise Up's message and code say what it refused. Re-send the donation; if it repeats, give the full message, including the Request-Id, to your MiSP, who can raise it with Fundraise Up.
A missing Recurring plans or Events permission does not stop a donation's transfer. Without Recurring plans, the installment still transfers, and its plan fields stay as the donation reported them. Without Events, new donations still arrive, but refunds and recurring plan changes found by the poll do not, and FUUP-AUTH-1003 appears in the error log.
Resolution: Read the Fundraise Up message and code in the error log and apply the matching cause above. When the message says to give it to your MiSP, include the Request-Id: they can review the subscription and the Fundraise Up key and take it further.
Fundraise Up could not be reached
FUUP-EXTN-1002 - Fundraise Up couldn't be reached ({network error}) — Request-Id: {requestId}. Check the API Url setting, then re-send the donation.
Description: A request to Fundraise Up got no answer: for example a network timeout, a DNS failure or an SSL problem.
Resolution: Confirm the API Url is correct and Fundraise Up is reachable. If the error came from the poll's own list read, the next poll reads the same donations again. If it came from one donation's transfer, a later poll does not read that donation again (unless it changes in Fundraise Up): re-send it from the error log or with a Manual Sync once Fundraise Up answers. For persistent connectivity issues, your MiSP can review the connection.
Fundraise Up had a temporary server error
FUUP-EXTN-1004 - Fundraise Up had a temporary server error (HTTP {status}) while the integration tried to {action}. This is a problem on Fundraise Up's side: re-send the donation once Fundraise Up answers again. If it still fails, give this message, with Request-Id {requestId}, to your MiSP, who can take it to iPaaS.com Support.
Description: Fundraise Up answered HTTP 500, 502, 503 or 504. This is a temporary problem on Fundraise Up's side, not a problem with your settings.
Resolution: Re-send the donation from the error log or with a Manual Sync once Fundraise Up answers again. If it still fails, give the full message, including the Request-Id, to your MiSP first.
Fundraise Up's limit of 3 requests at a time was reached
FUUP-EXTN-1005 - Fundraise Up's limit of 3 requests at a time was reached (code: concurrent_requests_limit_exceeded). The transfer is retried automatically after about 60 seconds. If this repeats, set Concurrent Connections to 1 or 2 on the subscription.
Description: Fundraise Up answered HTTP 429. Fundraise Up processes up to 3 requests at a time per account, across all of the account's API keys, live and test. The integration tells iPaaS.com to wait about 60 seconds, then the transfer is retried automatically. It can happen when the subscription's Concurrent Connections setting (an iPaaS.com setting, not one of this integration's) lets more than 3 transfers run at once, or when several subscriptions read the same Fundraise Up account and their Concurrent Connections add up to more than 3.
Resolution: Set Concurrent Connections to 1 or 2 on the subscription, and keep the total across all subscriptions on one Fundraise Up account at 3 or less.
Donation Poll (TO iPaaS.com)
The Donation Poll Days setting has an unrecognised value
FUUP-VALD-1004 - The subscription setting "Donation Poll Days" is "{value}". Set it to a whole number of days (for example 7), or 0 to import every donation, and save the subscription.
Description: Donation Poll Days limits the first poll of a new subscription to donations created in the last that many days. It accepts a whole number of days. Blank or 0 imports every donation. A negative number or a value that is not a number (for example -5 or "7 days") stops the first poll, so a typo never imports your whole donation history. The setting is read only on a first poll (while the subscription has no saved poll position); after that it is not read, so an invalid value entered later raises no error.
Resolution: Open the subscription settings, set Donation Poll Days to a whole number such as 7, or 0 to import every donation, and save. The next scheduled poll then runs as the first run.
The API key can't read Events
FUUP-AUTH-1003 - The Fundraise Up API key can't read Events, so refunds, edits and recurring plan changes made after a donation was created are not reaching iPaaS.com. New donations still transfer. In Fundraise Up, give the key Read permission on Events (for the same Live or Test mode as the Livemode setting), then dismiss this error.
FUUP-AUTH-1003 - The Fundraise Up API key can read Events again. Dismiss this error. The next poll reads the changes made while the permission was missing, from where it last read Events; if it had never read Events, re-send donations changed in that time by Manual Sync.
Description: Each poll reads Fundraise Up's event log to find donations that changed after they were created. Fundraise Up refused that read (HTTP 401 or 403), so the poll adds one item to the error log, with the external id FUUP-EVENTS-PERMISSION, and adds no second one while the permission is missing. New donations still transfer as normal; only the changes the poll reads from the event log (refunds, edits, recurring plan changes) are missing. The second message replaces the first on the same item when that item is re-sent from the error log after the key can read Events again; the next poll does not change or clear the item.
Resolution: In the Fundraise Up Dashboard, under Settings > API keys, give the key Read on Events, in the same mode (Live or Test) as the Livemode setting. Then dismiss this error; it is not removed automatically. Re-sending it from the error log first confirms the key can read Events: its text changes to the second message above, and you can dismiss it then. After the permission is back, the poll reads the changes made while it was missing, from where it last read Events. If it had never read Events, re-send the donations that changed in that time with a Manual Sync.
Donation Webhook (TO iPaaS.com)
Recurring plan's latest donation not found
FUUP-NFND-1001 - Fundraise Up recurring plan {planId} changed, but its latest donation is not among the newest 500 donations, so the change was not sent. Re-send that donation by Manual Sync with its Fundraise Up donation id (it starts with D), then dismiss this error.
Description: A Fundraise Up webhook said a recurring plan changed. The integration sends a plan change through the plan's most recent donation, and looks for it among the newest 500 donations. This plan's last donation is older than that, so nothing was sent.
Resolution: In Fundraise Up, open the recurring plan and note its most recent donation id (it starts with D). Re-send that donation with a Manual Sync of that id, then dismiss the error.
Donation and Supporter Transfer (TO iPaaS.com)
The Surcharge As Line Item setting has an unrecognised value
FUUP-VALD-1002 - The subscription setting "Surcharge As Line Item" is "{value}". Set it to Yes or No (blank means No) and save the subscription.
Description: The setting decides whether a processing fee the donor covered arrives as its own surcharge line. It accepts Yes, True, 1 or On (on) and No, False, 0 or Off (off). Any other value stops each donation transfer rather than guessing. iPaaS.com does not save a blank value for this setting (the previous value is kept); a subscription saved before the setting existed has no value, which counts as off.
Resolution: Open the subscription settings, set Surcharge As Line Item to Yes or No and save. Then re-send the donations that failed, from the error log or with a Manual Sync of each donation id: a later poll does not read them again.
Two or more iPaaS.com records match
FUUP-BIZL-1001 - {count} iPaaS.com Customers have the email {email}, so Fundraise Up supporter {id} can't be matched to one. Merge or correct the duplicate Customers in iPaaS.com, then re-send the donation.
FUUP-BIZL-1001 - {count} iPaaS.com Transactions have the Transaction Number {donation id}, so Fundraise Up donation {donation id} can't be matched to one. Remove or renumber the duplicates in iPaaS.com, then re-send the donation.
Description: Before creating a record, the integration looks for one that already exists: a Customer with the donor's email, or a Transaction whose Transaction Number is the donation id. It found two or more. It can't tell which one is right, so the transfer stops. It doesn't link the first one it finds.
Note: iPaaS.com keeps Customer emails unique and refuses a Transaction Number that another record already holds, so this error normally can't occur; it remains as a safeguard.
Resolution: In iPaaS.com, merge or correct the duplicate Customers, or remove or renumber the duplicate Transactions, so only one matches. Then re-send the donation from the error log or with a Manual Sync.
An existing record could not be linked
FUUP-INTL-1001 - Couldn't link Fundraise Up supporter {id} to the existing iPaaS.com Customer with the same email. Re-send the donation; if it persists, check that Customer's external ids for this subscription, or a duplicate Customer may be created.
FUUP-INTL-1001 - Couldn't link {Fundraise Up donation {id} / the payment of Fundraise Up donation {id} / the designation line of Fundraise Up donation {id}} to the existing iPaaS.com {Transaction with that Transaction Number / Transaction Payment / Transaction Line}. Re-send the donation; if it persists, check that record's external ids for this subscription, or a duplicate may be created.
FUUP-INTL-1001 - Couldn't link the surcharge line of Fundraise Up donation {id} to the existing iPaaS.com Transaction Line. Re-send the donation; if it persists, check that line's external ids for this subscription, or a duplicate line may be created.
Description: Before creating a record, the integration looks for one that already exists: a Customer with the donor's email, or a Transaction whose Transaction Number is the donation id, with its payment, designation line and surcharge line. It found one, but iPaaS.com didn't accept the link for this subscription, so the transfer stopped rather than create a duplicate. The payment and lines are linked first and the Transaction last, each only when not linked yet, so a re-send finishes the links that are missing and doesn't add a second payment or line.
Resolution: Re-send the donation. If the error repeats, open the named record in iPaaS.com and check its external ids for this subscription. Your MiSP can remove a stale link; then re-send the donation.
The donor's Customer could not be created
FUUP-INTL-1002 - The donor's Customer transfer failed, so Fundraise Up donation {id} was not transferred. Fix the Customer error logged for the same supporter, then re-send the donation.
Description: A donation transfers only after its donor exists in iPaaS.com as a Customer. The Customer transfer for this donor failed, so the donation was held back.
Resolution: Find the Customer error for the same supporter in the error log (for example a mapping or a required field), fix it, then re-send the donation.
An iPaaS.com call made by the integration failed
FUUP-INTL-1003 - An iPaaS.com API call the integration made ({action}) failed: {detail}
Description: While linking records the integration reads and writes iPaaS.com itself (looking up external ids, Customers by email, Transactions by number). One of those calls failed; the detail is iPaaS.com's own message.
Resolution: Usually temporary: re-send the donation. If it persists, the detail names the iPaaS.com problem; your MiSP can raise it with iPaaS.com Support.
An internal check failed
FUUP-INTL-1004 - The integration couldn't read the Fundraise Up id of a {type} record: the record was empty. Re-send the donation; if it repeats, give this message to your MiSP, who can take it to iPaaS.com Support.
FUUP-INTL-1004 - The integration couldn't read the Fundraise Up id of a {type} record ({record}). Re-send the donation; if it repeats, give this message to your MiSP, who can take it to iPaaS.com Support.
FUUP-INTL-1004 - The integration couldn't set the Fundraise Up id of a {type} record ({record}). Re-send the donation; if it repeats, give this message to your MiSP, who can take it to iPaaS.com Support.
FUUP-INTL-1004 - The Fundraise Up id "{id}" isn't a valid {record} id. Check the id you entered (for a Manual Sync), then re-send; if it repeats, give this message to your MiSP, who can take it to iPaaS.com Support.
FUUP-INTL-1004 - The Fundraise Up id "{id}" isn't a valid {type} id: it should be {a whole number / two parts separated by | / three parts separated by |}. Check the id, then re-send; if it repeats, give this message to your MiSP, who can take it to iPaaS.com Support.
FUUP-INTL-1004 - The integration couldn't name the iPaaS.com table for collection type {type}. Give this message to your MiSP, who can take it to iPaaS.com Support.
FUUP-INTL-1004 - The integration asked for an iPaaS.com API it doesn't use ({endpoint}). Give this message to your MiSP, who can take it to iPaaS.com Support.
Description: The integration checks its own work as it goes: that a record's Fundraise Up id can be read, set and understood, and that it names the right iPaaS.com table. One of those checks failed.
Resolution: If the message is about an id you entered for a Manual Sync, check the id and run it again. Otherwise re-send the donation. If it repeats, give the full message to your MiSP first, who can raise it with iPaaS.com Support.
Unsupported Collections and Manual Syncs
A FROM iPaaS.com collection was added
FUUP-VALD-1001 - Fundraise Up data comes TO iPaaS.com only; the integration can't create records in Fundraise Up. Remove the FROM iPaaS.com collection from this subscription.
FUUP-VALD-1001 - Fundraise Up data comes TO iPaaS.com only; the integration can't change records in Fundraise Up. Remove the FROM iPaaS.com collection from this subscription.
FUUP-VALD-1001 - Fundraise Up data comes TO iPaaS.com only, and Fundraise Up's API deletes nothing; the integration can't delete records in Fundraise Up. Remove the FROM iPaaS.com collection from this subscription.
Description: The subscription has a mapping collection that sends data FROM iPaaS.com to Fundraise Up (for example a Transaction or Customer collection). The integration only reads from Fundraise Up, so every transfer through that collection stops with this error, without calling Fundraise Up: nothing is written to Fundraise Up.
Note: The iPaaS.com portal doesn't offer a FROM iPaaS.com collection for this integration, so this error normally can't occur; it remains as a safeguard.
Resolution: Delete (or deactivate) the FROM iPaaS.com collection on the subscription, then dismiss the errors it left. If you need data in Fundraise Up, enter it in Fundraise Up itself.
A data type this integration doesn't transfer on its own
FUUP-VALD-1005 - Fundraise Up {type} records travel only with {its Donation (Transaction) / its Supporter (Customer)}. Sync the parent record instead, by its Fundraise Up id.
FUUP-VALD-1005 - This integration doesn't transfer {type} records. It transfers Donations (Transaction) and Supporters (Customer) TO iPaaS.com, with their child records. Remove the {type} collection, or the Manual Sync, from this subscription.
Description: A collection, Manual Sync or poll asked for a data type the integration doesn't transfer on its own. Payments and donation lines travel only with their Donation, and a Supporter Address only with its Supporter. Other data types are not transferred at all.
Resolution: For a Payment, a Supporter Address or a donation line, run the Manual Sync on the parent instead: the Donation id, or the Fundraise Up supporter id. For any other type, remove that collection or Manual Sync from the subscription.
Messages from earlier versions
Earlier versions of the integration logged most of these errors without a code, or with different wording. If your error log holds an older message, find its current code below and follow that entry.
Earlier message (begins with) | Current code |
Missing Setting: API Key is missing, or Missing Setting: API Url is missing | FUUP-AUTH-1001 |
Unable to process transfer. Reason: Unable to connect to subscription with id … | FUUP-AUTH-1002 when the API key is wrong; FUUP-EXTN-1005 when too many requests ran at once. Still shown, without a code, for an empty API Key (FUUP-AUTH-1001) or an unrecognised Livemode (FUUP-VALD-1003). |
TransferRequest is missing the payload data (in the activity log, with no error, when Livemode didn't match the API key) | FUUP-VALD-1006 |
FundraiseUp authentication failed: HTTP 401 | FUUP-AUTH-1002 |
FundraiseUp connection validation failed: HTTP | FUUP-AUTH-1002 |
FundraiseUp connection failed (no HTTP response) | FUUP-EXTN-1002 |
Error calling FundraiseUp. | FUUP-EXTN-1001 |
A network error message followed by "— Request-Id:" | FUUP-EXTN-1002 |
FundraiseUp transient error HTTP | FUUP-EXTN-1004 |
Object reference not set to an instance of an object (when Fundraise Up's limit of 3 requests at a time was reached) | FUUP-EXTN-1005 |
Unable to dynamically link to existing FundraiseUp customer, donation, donation payment or transaction line | FUUP-INTL-1001 |
Customer prerequisite for Donation {id} encountered an error | FUUP-INTL-1002 |
An iPaaS.com error message with no code, while the integration looked up or linked a record | FUUP-INTL-1003 |
Invalid data passed to … | FUUP-INTL-1004 |
Invalid key value at … | FUUP-INTL-1004 |
Unable to determine table name for mapping collection type | FUUP-INTL-1004 |
Unhandled endpoint type: | FUUP-INTL-1004 |
Call to … with unhandled parameters, when reading or setting a record's id | FUUP-INTL-1004 |
FundraiseUp integration is To iPaaS.com only — Create operations are not supported. (or Update operations) | FUUP-VALD-1001 |
FundraiseUp API does not support deletion for any resource. | FUUP-VALD-1001 |
Payment has no independent fetch — it is a child of Donation. | FUUP-VALD-1005 |
Unhandled mappingCollectionType: | FUUP-VALD-1005 |
Call to … with unhandled parameters, on a Manual Sync, a poll or a record read | FUUP-VALD-1005 |
FUUP-AUTH-1003, FUUP-VALD-1002, FUUP-VALD-1003, FUUP-VALD-1004, FUUP-VALD-1006, FUUP-BIZL-1001 and FUUP-NFND-1001 are checks added with the codes; they have no earlier message.
