> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration Options

> Configuration settings for the WeGive Blackbaud Raiser's Edge NXT integration: authentication, sync toggles, batch mode, constituent matching, and field mapping.

# Configuration Options

This guide covers the configuration options for the WeGive Blackbaud Raiser's Edge NXT integration.

## Authentication Configuration

### OAuth2 Settings

**Client ID**

* **Description**: The OAuth2 client identifier from your Blackbaud Sky API application
* **Required**: Yes
* **Format**: String (UUID format)

**Client Secret**

* **Description**: OAuth2 client secret
* **Required**: Yes
* **Security**: Encrypted at rest, never displayed after entry

**Subscription Key**

* **Description**: Blackbaud Sky API subscription key for API access
* **Required**: Yes
* **Location**: Found in your Blackbaud Developer account

**Environment ID**

* **Description**: Your Raiser's Edge NXT environment identifier
* **Required**: Yes
* **Location**: Administration > Application Settings in Raiser's Edge NXT

**Redirect URI**

* **Description**: OAuth2 callback URL for authentication completion — auto-configured, not user-editable.

## Synchronization Settings

Each of the toggles below can be turned on or off independently per organization; all default to enabled. Sync frequency is not a per-object setting — see Sync Cadence below.

### Pull Configuration (Blackbaud → WeGive)

| Setting | Description |
| - | - |
| Pull Donors | Sync individual constituent records from Blackbaud |
| Pull Companies | Sync organization/company constituent records |
| Pull Campaigns | Sync fundraising campaigns and appeals |
| Pull Funds | Sync fund and designation information |
| Pull Transactions | Sync gift records (donations, pledge payments, recurring gift payments) |
| Pull Recurring Gifts | Sync recurring donation schedules |
| Pull Appeals | Sync Raiser's Edge appeals |

<Note>
  Household constituent records are not synced by this integration — Blackbaud constituents come into WeGive as either individual donors or company/organization records.
</Note>

### Push Configuration (WeGive → Blackbaud)

| Setting | Description |
| - | - |
| Push Donors | Create and update individual constituent records in Blackbaud — real-time |
| Push Companies | Create and update company constituent records in Blackbaud — real-time |
| Push Transactions | Create and update gift records in Blackbaud from WeGive donations — real-time by default, see Batch Mode below |
| Push Scheduled Donations | Create and update recurring gift records in Blackbaud — real-time |

<Note>
  Funds and campaigns referenced by a transaction need to exist in Raiser's Edge (with the Raiser's Edge ID linked on the WeGive side) before that transaction can sync — WeGive doesn't create a missing fund or campaign automatically on push. Pre-create these directly in Raiser's Edge.
</Note>

<Note>
  Communication list / donor segment sync isn't part of this integration.
</Note>

## Batch Mode vs. Real-Time Transaction Push

**Real-time (default)**: each new, updated, failed, or refunded transaction pushes to Raiser's Edge individually, as it happens.

**Batch mode (opt-in)**: individual real-time transaction pushes are suppressed. Instead, a daily scheduled job runs once per day and pushes the prior day's new card/bank transactions — plus any that newly failed or were refunded — to Raiser's Edge as a single named gift batch (`"WeGive Import <date>"`), tied to your organization's own timezone day boundary.

<Info>
  Donor and company pushes always happen in real time regardless of this setting — batch mode only affects transaction push timing.
</Info>

## Sync Cadence

Blackbaud pulls run on a fixed platform-wide schedule — every 15 minutes for every organization with the integration enabled. There's no per-organization frequency setting to adjust this interval.

## Constituent Matching

Constituent matching between WeGive and Blackbaud is by Raiser's Edge ID — an exact match on the stored constituent ID from a prior sync, with no name/email/phone fallback. This means duplicate prevention covers records created through the WeGive integration; a gift or constituent created in Blackbaud through another channel (e.g. a manually staged CSV import) has no shared identifier for WeGive's sync to recognize.

## Field Mapping

Field mapping for constituents, gifts, recurring gifts, funds, companies, households, and appeals is set up automatically with a default rule set when the integration is first connected.

<Note>
  Push-side campaign attribution runs through Appeals, not Campaign ID — see [Campaign Mapping](/external/onboarding/blackbaud/data-mapping/campaign#appeals-map-to-campaign-fundraisers-not-a-nested-campaign-sub-object) and [Gift Mapping](/external/onboarding/blackbaud/data-mapping/gift#fund-and-campaign-attribution) for the specifics. If you're configuring this integration for campaign-level reporting on pushed gifts, link your campaign fundraisers' Appeals rather than relying on Campaign ID alone.
</Note>

Default payment-method mappings:

| WeGive | Raiser's Edge |
| - | - |
| Card | Credit Card |
| Bank | Check (WeGive labels this payment method "ACH") |

## Retry Behavior

Failed API requests retry automatically with exponential backoff (a handful of attempts) as a fixed platform policy — this isn't a per-organization tunable setting.

## Getting Help

For configuration assistance:

* **WeGive Support**: [support@wegive.com](mailto:support@wegive.com)
* **Blackbaud Resources**: [Sky API Documentation](https://developer.blackbaud.com/skyapi/)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.