Overview

This article catalogs the errors subscribers can encounter when the Fundraise Up integration calls the Fundraise Up API and surfaces them in iPaaS.com error logs. Each error carries a stable code you can search for on this page, followed by its trigger condition and remediation guidance. Errors appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs.

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 set up and manages your iPaaS.com integration.

The Fundraise Up integration is read-only in v1.0.1 — it polls Fundraise Up for donations and supporters and writes them into iPaaS.com. All Fundraise Up API error responses follow a uniform JSON shape:

{
  "error": {
    "message": "<human-readable explanation>",
    "code": "<machine-readable error code>"
  }
}

Every Fundraise Up API response carries a request-id header (lowercase — include it when contacting Fundraise Up support). The integration treats several HTTP responses as expected and consumes them silently — most notably 404 on individual record lookups ("record deleted at source") and the supporter-not-found path on a Donation transfer (anonymous-donation placeholder). Those are not errors; see Fundraise Up Known Limitations.

Supported Flows

Authentication and connection validation
Donation polling and transfer

Error Collection

Authentication and connection validation

A required connection setting is missing

FUUP-AUTH-1001 - Missing Setting: {API Key or API Url} is missing

Description: The integration could not establish the connection because a required subscription setting — the API Key or the API Url — is empty. This fires before any call to Fundraise Up is attempted.
Resolution: Open the iPaaS.com subscription settings and confirm both the API Key and API Url presets are populated (the API Url default is Fundraise Up's API base). Save the subscription and re-establish the connection.

The connection could not be validated

FUUP-AUTH-1002 - {connection-validation failure detail}

Description: The integration validated the connection against Fundraise Up (a lightweight probe, GET /v1/donations?limit=1) and the validation did not succeed. The logged message carries the underlying reason returned by Fundraise Up.
Resolution: Confirm the API Key is a currently-active Fundraise Up key for the matching environment (a live-mode key cannot be used with Livemode=false, and vice versa), and that the API Url is correct. Re-authorize the connection. If it persists, your MiSP can review the connection and the Fundraise Up key.

Fundraise Up rejected the request

FUUP-EXTN-1001 - Error calling Fundraise Up.{action}: {message} (code: {code}) (HTTP {status}) — Request-Id: {requestId}

Description: Fundraise Up returned an error response for the request. The logged message includes Fundraise Up's message, machine code, HTTP status, and the request-id. The most common conditions are below.
Common causes and resolutions:
- Invalid or revoked API key — {"error":{"message":"No valid token is provided.","code":"unauthorized"}} (HTTP 401). The API Key preset is missing, malformed, or revoked. Verify it matches a currently-active Fundraise Up key (Settings → API keys); if it was rotated, copy the new key into the subscription and save. Ensure the key's environment matches the Livemode preset.
- Insufficient API key permissions — {"error":{"message":"Permission denied.","code":"forbidden"}} (HTTP 403). The key lacks a required scope. In the Fundraise Up dashboard (Settings → API keys), confirm the key has at least Donations: Read and Supporters: Read; if not, create a new key with the correct scopes, paste it into the subscription, save, then revoke the old key.
Resolution: Read the Fundraise Up message and code in the error log and apply the matching cause above. If the condition is not a credential or scope issue you can correct, your MiSP can review the subscription and the Fundraise Up key.

Donation polling and transfer

Fundraise Up request or transport error

FUUP-EXTN-1002 - {transport error detail} — Request-Id: {requestId}

Description: A low-level request error occurred while communicating with the Fundraise Up API — for example a network timeout, DNS failure, or SSL issue. The technical log carries the underlying detail and the request-id.
Resolution: Retry the transfer (the affected records reappear on the next poll). Confirm the API Url is correct and Fundraise Up is reachable. For persistent connectivity issues, your MiSP can review the connection.

Batch run error

FUUP-EXTN-1003 - Received an exception during batch run on of {Action}. {first exception message}

Description: The integration runs several Fundraise Up calls together as a batch; one of the calls failed and the first underlying error is surfaced.
Resolution: Read the underlying error in the message. If it references a specific Fundraise Up condition (see FUUP-EXTN-1001), correct it and retry. If it is not actionable, your MiSP can review the batch and the Fundraise Up response.

Automatically handled — no action required. Two Fundraise Up conditions are transient and rescheduled by iPaaS.com automatically, so they are not errors you need to act on:

Concurrency limit (HTTP 429) — Fundraise Up allows 3 parallel requests per account across all keys (concurrent_requests_limit_exceeded). The default Concurrent Connections preset of 1 keeps requests single-threaded so this is not reached in normal operation; it can fire if multiple subscriptions target the same Fundraise Up account and their Concurrent Connections values sum above 3. Keep each subscription's Concurrent Connections at 1 (or 2), and ensure the sum across subscriptions on one account does not exceed 3.
Server error (HTTP 500/502/503/504) — a transient Fundraise Up platform issue; the affected transfer reappears on the next poll. If 5xx errors persist for over an hour, check Fundraise Up's status channels and, if confirmed healthy upstream, capture the request-id and raise it with your MiSP.

Errors documented for completeness — reserved for future write features (not yet reachable)

The integration is read-only in v1.0.1, so the Fundraise Up responses below cannot be triggered today — they only fire on outbound write operations (e.g., POST /v1/donations). They are documented so the catalog is ready when a write surface is added; codes will be assigned at that time. Subscribers will not encounter them in normal operation.

Payment account not configured — {"error":{"message":"The organization must have an active Stripe account.","code":"payment_account_required"}}. Returned by POST /v1/donations against an account with no active Stripe connection.
Required parameter missing — {"error":{"message":"The \"supporter\" parameter is required.","code":"parameter_required","parameter":"supporter"}} (and the supporter.first_name / payment_method variants). Returned by POST /v1/donations when a required field is absent; the parameter field names the exact missing (possibly nested) field path.

Reporting an issue

If you encounter an error not covered above, capture the iPaaS.com Subscription ID, the Fundraise Up donation id (if applicable), and the iPaaS.com error log entry including the Fundraise Up request-id header value, and raise it with your MiSP first. For Fundraise Up–side anomalies, your MiSP can escalate to Fundraise Up support with the request-id attached.

Fundraise Up Error Messages