Skip to main content
Use the @bijection/connectors/blackbaud entrypoint to declare Blackbaud Raiser’s Edge NXT resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Constituents

changes: Constituents by last_modified

The following example matches configuration standard.

Configuration: standard

Case: blackbaud/constituents/changes/standard. Connection and resource configuration are declared by this exact case. Credential kind: blackbaud-sky. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: constituents
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. constituents.changes reads GET /constituent/v1/constituents?last_modified=<T>&limit=100 and follows the stated next_link (its sort_token and offset only). A finished pass carries the latest date_modified. Hard-deleted constituents are absent from every list, so nothing is withdrawn; the delete webhook is not built. SKY needs a refreshed OAuth bearer token AND the developer’s Bb-Api-Subscription-Key on every request. The credential is an oauth_refresh envelope over the authorization-code grant whose resource_headers hold the subscription key; the host writes both and keeps the subscription key out of every guest value:
Built from the provider’s published API documentation; nothing here has run against Blackbaud Raiser’s Edge NXT or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.