Connect Raiser’s Edge NXT using the Fundraise Up API

To build this connection, you'll need:

• Access to your Fundraise Up Dashboard with Organization Administrator role (required to manage API keys).
• Admin access to your Raiser’s Edge NXT environment.

1. Go to Dashboard > Settings > API keys.
2. Click Create API key.
3. Enter a descriptive name (for example, "RE NXT Integration").
4. Choose Live data to sync real data. Use Test data if you’re testing.
5. Select Retrieve donation data permission.
6. Click Create API key.

If you're working with subaccounts, make sure you generate the API key from the correct subaccount.

Include your API key in the Authorization header using Bearer authentication:

1curl -H "Authorization: Bearer YOUR_API_KEY" \
2     https://api.fundraiseup.com/v1/donations
3

All requests must use HTTPS. HTTP requests are not accepted.

Your CRM sync will use these Fundraise Up entities:

• Donations. Includes amount, currency, status, type, timestamp, and unique Fundraise Up identifiers.
• Supporters. Name, email, phone, mailing address, and preferences.
• Recurring plans. Frequency, status, start date, donation amount, and next installment date.
• Campaigns. Used to categorize donations.
• Designations. Specifies the program or fund selected by the supporter.
• Tributes. Optional tribute data (in honor or in memory of someone).

Each object is accessible through the API. Details on structure and fields can be found in the API reference.

Your integration service will need to periodically poll (query) the Fundraise Up API to check for new or updated records since the last sync.

Use GET requests to fetch data from these API endpoints.

• GET /v1/donations
• GET /v1/supporters
• GET /v1/recurring_plans
• GET /v1/campaigns
• GET /v1/designations
• GET /v1/tributes

Use limit, starting_after, and ending_before for pagination.

• GET /v1/donations/{donation_id}
• GET /v1/supporters/{supporter_id}
• GET /v1/recurring_plans/{plan_id}
• GET /v1/campaigns/{campaign_id}
• GET /v1/designations/{designation_id}
• GET /v1/tributes/{tribute_id}

These are useful for re-sync attempts or fetching full record detail after a list query.

If you prefer event-based syncing over polling, you can use Zapier to listen for Fundraise Up triggers.

Zapier can then trigger a sync job in your system. Fundraise Up doesn’t support direct webhooks to external URLs. Learn more about Zapier integration →

To sync historical data when first setting up the integration or backfilling your CRM, you'll need to perform a historical data sync.

To load past records:

1. Use starting_after and ending_before parameters with an existing object ID.
2. Fetch data in batches using limit. This parameter specifies the number of records to display per page, ranging from 1 to 100.
3. Process each batch sequentially.

Field mapping is a critical step where you define how Fundraise Up data fields correspond to fields in the Raiser’s Edge NXT. Correct field mapping ensures that Fundraise Up data is stored in the right places in your CRM and avoids sync errors.

• Identify corresponding objects. Define which CRM objects correspond to Fundraise Up entities (for example, donation → gift, supporter → constituent).
• Match data types. Ensure the data types are compatible. Transform values as needed (for example, string to picklist).
• Handle required fields. Identify which fields are required in Raiser’s Edge NXT and ensure you supply values, using defaults if needed.
• Store Fundraise Up IDs. Always store Fundraise Up’s unique IDs in your CRM. These are essential for update logic and deduplication.
• Include custom fields. Map any custom fields you collect for supporters or donations.

This table is illustrative. Adapt field mappings to match your CRM configuration.

Your CRM should prevent duplicate records by using Fundraise Up IDs as primary keys.

• On sync, check if a record already exists using the Fundraise Up ID (for example, Donation ID or Supporter ID).
• If found, update it. If not, create a new record.
• If IDs are missing, use fallback matching logic such as email address and full name.

Fundraise Up's API has usage limits. See the rate limit section for details.

Include retry handling and backoff logic in your integration.

When sending data to Raiser’s Edge NXT using a custom integration, keep these platform-specific behaviors in mind:

• Receipt number: Fundraise Up’s Receipt ID cannot populate Raiser’s Edge NXT’s locked Receipt Number field. Map it to a custom field on the Gift record in Raiser’s Edge NXT (for example, Fundraise Up Receipt ID).
• Canceled recurring plans: ReNXT does not support reactivating canceled recurring plans. If a supporter resumes a plan, create a new recurring gift in Raiser’s Edge NXT.
• Direct debit donations sync: For direct debit methods like ACH and SEPA, donations only sync to Raiser’s Edge NXT after the payment settles — when the status in Fundraise Up changes to succeeded. This can take several days.
• Refunds: When a donation is refunded in Fundraise Up, this does not automatically update the original gift record’s status to refunded in Raiser’s Edge NXT. Manually create a corresponding refund adjustment or update the gift's status in Raiser’s Edge NXT to reflect the refund accurately.
• Batching: Fundraise Up doesn’t assign donations to batches in Raiser’s Edge NXT. Each donation is created as a separate gift record.
• Bulk sync: Raiser’s Edge NXT doesn’t support bulk inserts — each record must be synced individually. Manual re-syncs using the API will require custom logic.
• Deletions: Donations synced from Fundraise Up to Raiser’s Edge NXT may not be deletable through the web UI. Consult Raiser’s Edge NXT documentation for data modification and deletion policies.
• Failed donations: Donations with failed status aren’t synced to Raiser’s Edge NXT, since they aren’t completed gifts. You may choose to log these elsewhere based on your data policies.

For endpoint details, request formats, and examples, refer to our API documentation.

If building a custom integration isn't feasible, consider these alternatives:

• Omatic Cloud: Pre-built integration platform with special pricing for Fundraise Up customers.
• Zapier: Event-driven automation with Fundraise Up triggers.
• Importacular: Database-level integration for smaller organizations.
• Data exports: Manual CSV exports from Fundraise Up for periodic imports.

Each option has different levels of automation and technical complexity to match your organization’s needs.