Native RE NXT connector versus a custom API integration

For GiveCampus integrations and API.

The built-in Blackbaud RE NXT integration is a separate setup path from developing a custom client for the generic GiveCampus API. Where the school's integration is enabled, an authorized administrator connects Blackbaud through its authorization flow and configures the available constituent import, gift export and event export options. This native path does not inherently require the school to write its own API scripts or buy a separate middleware product merely because a general API article discusses those options.

It still requires setup: confirm entitlement and authorization, choose the intended Lookup ID versus System ID mapping, configure funds and the desired flows, and review sample export runs/errors. Gift exports and event participant exports have separate settings; “connected” does not mean every kind of gift, fee and registration is already synchronized. Donor-covered fees and processor fees are distinct fields; confirm the desired accounting treatment and supported mapping instead of promising one universal fee-record export.

For unsupported fields or workflows, a custom integration or another approved process may still be necessary. Contract inclusion, third-party charges and implementation timelines require account-specific confirmation. A generic API article does not confirm those commercial facts or negate the existence of the native connector.