Skip to main content

Fundraise Up Error Messages

Fundraise Up Error Messages

This document catalogs the error responses subscribers can encounter when the Fundraise Up integration calls the Fundraise Up API and surfaces them in iPaaS.com error logs. Each entry includes the verbatim Fundraise Up response shape, the trigger condition, and remediation guidance.

The Fundraise Up integration is read-only in v1.0.0 — it polls Fundraise Up for donations and supporters and writes them into iPaaS.com. Errors below are grouped into:

  • Errors reachable from the v1.0.0 integration flow — what subscribers can encounter during normal operation (the bulk of the catalog).

  • Errors documented for completeness — reserved for future write features — Fundraise Up validation errors that only fire on outbound write operations (e.g., creating a donation through the API), which the integration does not currently perform. They are documented so the catalog is ready the day a write surface is added.

All Fundraise Up error responses follow a uniform JSON shape:

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

parameter_required responses include an additional parameter field naming the missing field path.

Every Fundraise Up API response carries a request-id header (lowercase — important to include when contacting Fundraise Up support).

Note on current vs. canonical error text. The error messages in this article reflect Fundraise Up's documented response shape. The integration's error log may currently show a more generic message for some 4xx responses until the iPaaS.com error-passthrough improvements land (see the Activity Tracker entry's request-id and the original Fundraise Up response body for the canonical text in the meantime).

Supported Flows

This article covers only error responses subscribers see in iPaaS.com error logs. The Fundraise Up integration treats several HTTP responses as expected and consumes them silently — most notably 404 on individual record lookups (handled as "record deleted at source") and the supporter-not-found path on a Donation transfer (handled by the anonymous-donation placeholder mechanism). Those behaviors are not errors; for the full integration-behavior reference see Fundraise Up Known Limitations and the per-collection Donation Mapping Documentation and Supporter Mapping Documentation.

Authentication and connection validation

Invalid or revoked API key

Error message: No valid token is provided.

Fundraise Up response:

{"error":{"message":"No valid token is provided.","code":"unauthorized"}}

  • Description: Fundraise Up returns HTTP 401 Unauthorized when the API key in the iPaaS.com subscription's API Key preset is missing, malformed, or has been revoked. The error fires on the initial connection-validation probe (GET /v1/donations?limit=1) and on any subsequent request.

  • Resolution:

  • Open the iPaaS.com subscription's settings page and verify the API Key preset matches a currently-active Fundraise Up API key.

  • If the API key was rotated in Fundraise Up's dashboard, copy the new key into the iPaaS.com subscription preset and save the subscription.

  • If the Livemode preset was changed on the iPaaS.com subscription, ensure a key issued for the matching environment is in place — a live-mode key cannot be used with Livemode=false and vice versa.

  • If the error persists after key replacement, contact iPaaS.com Support.

Insufficient API key permissions

Error message: Permission denied.

Fundraise Up response:

{"error":{"message":"Permission denied.","code":"forbidden"}}

  • Description: Fundraise Up returns HTTP 403 Forbidden when the API key is valid but does not have the permissions required for the requested resource — most commonly, the key was created without the Donations: Read scope or Supporters: Read scope.

  • Resolution:

  • Sign in to the Fundraise Up dashboard and open Settings → API keys.

  • Verify the key's permission scopes include at minimum Donations: Read and Supporters: Read.

  • If scopes are insufficient, create a new key with the correct permissions, paste it into the iPaaS.com subscription preset, save the subscription, then revoke the old key in Fundraise Up.

Donation polling and transfer

Fundraise Up rate limit exceeded (concurrency limit)

Error message: Fundraise Up concurrency limit exceeded — too many parallel requests.

Fundraise Up response:

{"error":{"message":"You have exceeded the number of allowed concurrent requests.","code":"concurrent_requests_limit_exceeded"}}

  • Description: Fundraise Up enforces a concurrency-based rate limit of 3 parallel API requests per account, across all endpoints and all API keys (live and test combined). When more than 3 requests are in flight simultaneously, additional requests are rejected with HTTP 429 Too Many Requests and the error code concurrent_requests_limit_exceeded. The integration's default Concurrent Connections preset of 1 keeps requests single-threaded so this limit is not reached in normal operation; the error can fire if multiple iPaaS.com subscriptions targeting the same Fundraise Up account aggregate above 3 parallel.

  • Resolution:

  • Open the Fundraise Up Connections and Settings reference and confirm the subscription's Concurrent Connections preset is 1 (recommended) or 2. Do not exceed 2.

  • 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), confirm the sum of their Concurrent Connections values does not exceed 3.

  • The integration treats 429 as a transient error and reschedules the affected transfer automatically — no subscriber intervention is required unless 429s recur with healthy concurrency settings.

Fundraise Up server error (transient)

Error message: Fundraise Up server error — transient. Will retry automatically.

  • Description: Fundraise Up returns HTTP 500, 502, 503, or 504 during periods of upstream platform unavailability or processing errors on the Fundraise Up side. These are rare. The integration classifies them as transient and reschedules the affected transfer through the iPaaS.com scheduler's standard retry policy.

  • Resolution: Generally no action is required — the affected transfer reappears on the next poll cycle. If 5xx errors persist for more than an hour:

  • Check Fundraise Up's status / support channels for ongoing platform issues.

  • If Fundraise Up confirms no upstream issue, capture the request-id value from the iPaaS.com Activity Tracker entry and contact iPaaS.com Product Support.

Errors documented for completeness — reserved for future write features

The Fundraise Up integration is read-only in v1.0.0. The error responses below can only be triggered by outbound write operations (e.g., POST /v1/donations) which the integration does not currently perform. They are documented so the catalog is ready the day a write surface is added; subscribers will not encounter them in normal operation.

Payment account not configured (write-only)

{"error":{"message":"The organization must have an active Stripe account.","code":"payment_account_required"}}

  • Description: Returned by POST /v1/donations against a Fundraise Up account with no active Stripe connection (a test-mode account that has not completed Stripe onboarding, or a live-mode account that has lost its Stripe connection).

  • Resolution: Not reachable from the v1.0.0 integration flow. If a future write surface is added, the resolution would be to complete the Fundraise Up account's Stripe onboarding before the integration attempts donation creation.

Required parameter missing — supporter (write-only)

{"error":{"message":"The \"supporter\" parameter is required.","code":"parameter_required","parameter":"supporter"}}

  • Description: Returned by POST /v1/donations with no supporter field in the request body.

  • Resolution: Not reachable from the v1.0.0 integration flow.

Required parameter missing — supporter.first_name (write-only)

{"error":{"message":"The \"supporter.first_name\" parameter is required.","code":"parameter_required","parameter":"supporter.first_name"}}

  • Description: Returned by POST /v1/donations with a supporter object that omits first_name. The parameter field uses a dotted path naming the exact missing nested field — useful for surfacing precise remediation messages once a write surface exists.

  • Resolution: Not reachable from the v1.0.0 integration flow.

Required parameter missing — payment_method (write-only)

{"error":{"message":"The \"payment_method\" parameter is required.","code":"parameter_required","parameter":"payment_method"}}

  • Description: Returned by POST /v1/donations with no payment_method field.

  • Resolution: Not reachable from the v1.0.0 integration flow.

Reporting an issue

If you encounter an error not covered above:

  1. 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 response header value.

  2. Open a support ticket via https://support.ipaas.com/en/ referencing integration_id 12151.

  3. For Fundraise Up–side anomalies, escalate to https://fundraiseup.com/support/ with the request-id value attached.

Related Documents

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