.png)
Blackbaud Raiser's Edge NXT Integration Guide
Integrate Raiser's Edge NXT with enterprise systems through the Blackbaud SKY API, OAuth 2.0, selected webhooks, and orchestrated Martini workflows.
Blackbaud Raiser's Edge NXT integration options at a glance
Blackbaud Raiser's Edge NXT integrations primarily use the Blackbaud SKY API, a REST-based platform for retrieving and updating supported Constituents, Gifts, Funds, Campaigns, Appeals, and Actions. Applications generally authenticate with OAuth 2.0 and may also need an API subscription key, application registration, scopes, and organization-specific permissions. Selected resources and events support webhook-style notifications, while larger synchronizations can use pagination, scheduled polling, controlled batches, and checkpoints. Resource-specific attachment operations may be available. Martini can consume the SKY API, receive supported notifications, map and transform objects, apply business rules, and expose normalized APIs to downstream systems.
| Integration point | Supported by Blackbaud Raiser's Edge NXT? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | The Blackbaud SKY API is the primary interface for retrieving and updating supported Constituents, Gifts, Funds, Campaigns, Appeals, and Actions. | Martini can consume REST endpoints, manage request sequencing, map responses, apply conditions, and expose normalized APIs to internal applications. |
| Webhooks / outbound callbacks | Limited | SKY API webhook-style notifications are available for selected supported resources and events; they are not a universal stream for every object or field change. | Martini can expose an API or webhook-consuming workflow, validate notifications, retrieve the current resource, and route the result to downstream systems. |
| Bulk / async / batch APIs | Limited | Collection operations and product-specific batch concepts may support larger workloads, but a universal bulk API for all Raiser's Edge NXT objects should not be assumed. | Martini can orchestrate paginated reads, controlled request batches, checkpoints, throttling responses, and idempotent upserts. |
| File / attachment APIs | Limited | Attachment and document operations may be available for specific SKY API resources and permissions. | Martini can transfer supported file content or metadata, subject to the resource's documented response format, size limits, and permissions. |
| Authentication | Yes | Applications generally use OAuth 2.0, registered application credentials, scopes, user permissions, and an API subscription key where required. | Martini can store client credentials, subscription keys, refresh tokens, and environment values as secrets and use them in authenticated workflows. |
| GraphQL APIs | Not confirmed | No official Blackbaud SKY API GraphQL documentation was identified for Raiser's Edge NXT. | Martini should use the documented REST interface rather than assuming GraphQL support. |
| SOAP APIs | Not confirmed | No official Blackbaud SKY API SOAP documentation was identified for Raiser's Edge NXT. | Martini should use the documented REST interface rather than assuming SOAP support. |
| Database access | No | Direct access to the Raiser's Edge NXT cloud database is not a standard confirmed customer integration method. | Martini can use the SKY API and supported notifications or exports instead of attempting direct JDBC access. |
How Blackbaud Raiser's Edge NXT exposes data and business events
Blackbaud SKY REST APIs
The Blackbaud SKY API is the primary documented integration mechanism for Raiser's Edge NXT. It provides REST operations for supported objects and actions, with access determined by application registration, OAuth authorization, scopes, user permissions, organization configuration, and enabled products.
Martini implementation pattern
Martini implementation pattern: A workflow obtains or refreshes an OAuth access token, adds required application headers such as an API subscription key where applicable, calls the relevant SKY API endpoint, handles pagination and status codes, maps the response, and writes the result to a target system or exposes it through a Martini API.
Implementation sequence
Blackbaud Webhooks
Blackbaud SKY API provides webhook-style notifications for selected supported resources and events. Coverage, payload shape, subscription requirements, and event types are resource-specific, so notifications should not be treated as a complete event stream.
Martini implementation pattern
Martini implementation pattern: An exposed Martini API receives the notification, validates and logs the request, identifies the affected resource, retrieves the current object from the SKY API, and invokes downstream processing. A scheduled reconciliation workflow supplements notifications where coverage is incomplete.
Implementation sequence
Collection and Batch Processing
SKY API collection operations and product-specific batch concepts can support larger synchronizations, but universal bulk processing for every Raiser's Edge NXT object is not confirmed.
Martini implementation pattern
Martini implementation pattern: A scheduled workflow reads pages or controlled batches, stores a checkpoint or watermark, limits concurrency, responds to throttling, and performs idempotent upserts. The exact batch operation must be verified for each resource before implementation.
Implementation sequence
Resource-specific File and Attachment APIs
File and attachment operations may be available for specific SKY API resources. The relevant resource must be checked to determine whether the response contains binary content, metadata, or a download reference.
Martini implementation pattern
Martini implementation pattern: A workflow calls the supported attachment endpoint, transfers metadata or content according to the resource contract, validates content type and size, and records the source identifier and transfer status for retry and audit purposes.
Implementation sequence
Common Blackbaud Raiser's Edge NXT integration patterns
Pattern 1: Sync Constituents to Salesforce
When to use this pattern
Use this pattern when fundraising and CRM teams need a shared view of constituent relationships. A scheduled or supported event-driven workflow retrieves new or changed Constituents, maps names, contact details, communication preferences, and identifiers, and performs idempotent Salesforce upserts. Field ownership and selective reverse synchronization should be agreed before enabling bidirectional flows.
Integration direction
Example Mapping
| Blackbaud Raiser's Edge NXT Field | Canonical Field | Target Field |
|---|---|---|
| constituent_id | externalConstituentId | Blackbaud Constituent ID |
| name | displayName | Name |
| email_address | primaryEmail | |
| communication_preferences | communicationPreferences | Email Opt Out / Consent fields |
Martini implementation pattern
Martini calls the SKY API, follows pagination or retrieves the resource after a notification, validates identity and consent data, applies field-ownership rules, and upserts Salesforce records. The workflow stores cross-reference identifiers, retries transient failures, and routes duplicate or ambiguous matches for review.
Martini capabilities used
- workflows
- API consumption
- OAuth configuration
- data mapping
- business rules
- idempotent upserts
- error handling
Pattern 2: Send Gifts to NetSuite
When to use this pattern
Use this pattern when fundraising transactions must be reconciled with financial operations. Martini retrieves Gifts and related Funds, Campaigns, Appeals, and Constituents, normalizes financial fields, and sends approved records to NetSuite while preventing duplicate postings.
Integration direction
Example Mapping
| Blackbaud Raiser's Edge NXT Field | Canonical Field | Target Field |
|---|---|---|
| gift_id | sourceTransactionId | External ID |
| amount | transactionAmount | Transaction Amount |
| fund_id | fundReference | Fund / Class reference |
| gift_date | transactionDate | Transaction Date |
Martini implementation pattern
A scheduled workflow uses a persisted watermark, paginates through Gifts, resolves related objects, validates required financial mappings, and performs an idempotent NetSuite write. Before retrying an ambiguous failure, it checks whether the target transaction already exists and records exceptions for reconciliation.
Martini capabilities used
- scheduled workflows
- pagination
- data mapping
- relationship resolution
- validation
- business rules
- checkpointing
- retry handling
Pattern 3: Process Supported Gift or Constituent Notifications
When to use this pattern
Use this pattern when a selected SKY API webhook event can reduce the latency of constituent or fundraising processing. Because webhook coverage is selective and payloads may be incomplete, the workflow retrieves the current object and uses scheduled reconciliation for completeness.
Integration direction
Example Mapping
| Blackbaud Raiser's Edge NXT Field | Canonical Field | Target Field |
|---|---|---|
| event.resource_id | sourceObjectId | External ID |
| event.resource_type | objectType | Integration object type |
| last_modified | sourceModifiedAt | Modified On |
| constituent_id | constituentReference | Contact reference |
Martini implementation pattern
Martini exposes a controlled API endpoint, validates and logs the notification, retrieves the current SKY API resource, applies object-specific rules, and forwards a normalized message or API request to Dynamics 365. Duplicate notifications are safely reprocessed using source IDs, while failures enter retry or reconciliation handling.
Martini capabilities used
- API exposure
- webhook consumption
- API consumption
- data mapping
- deduplication
- business rules
- monitoring
- error handling
Pattern 4: Publish Campaign and Appeal Data
When to use this pattern
Use this pattern when external reporting or communications applications need a normalized view of fundraising structure. The workflow retrieves Campaigns, Appeals, Funds, and related fundraising information, translates Blackbaud classifications into the target hierarchy, and routes missing mappings for review.
Integration direction
Example Mapping
| Blackbaud Raiser's Edge NXT Field | Canonical Field | Target Field |
|---|---|---|
| campaign_id | sourceCampaignId | Campaign ID |
| campaign_name | campaignName | Campaign Name |
| appeal_id | sourceAppealId | Audience or campaign reference |
| fund_id | fundReference | Fund classification |
Martini implementation pattern
A scheduled Martini workflow retrieves supported objects, maintains a checkpoint, normalizes classification values, validates consent and target requirements, and publishes only approved data. Mapping exceptions are isolated from successful records, and retries resume from the stored synchronization state.
Martini capabilities used
- scheduled workflows
- API consumption
- checkpointing
- data transformation
- validation
- conditional routing
- exception handling
Applications commonly integrated with Blackbaud Raiser's Edge NXT
Blackbaud Raiser's Edge NXT can be integrated with fundraising, relationship-management, communications, financial, and reporting applications. Exact object coverage, write operations, and product-to-product support should be confirmed for each organization's subscriptions and API permissions.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize Constituents, donor relationships, campaigns, and engagement information between fundraising and CRM teams. | Blackbaud Raiser's Edge NXT → Martini → Salesforce | Use scheduled SKY API reads or supported notifications, map Constituents and related fundraising data to Salesforce Contacts or Accounts, and perform idempotent upserts using stable cross-reference identifiers. Apply field-ownership rules for any selective reverse synchronization. |
| Microsoft Dynamics 365 | Bring constituent and fundraising information into broader relationship-management and finance processes. | Blackbaud Raiser's Edge NXT → Martini → Microsoft Dynamics 365 | Retrieve permitted SKY API objects, normalize constituent and fundraising fields, apply matching and ownership rules, and write validated data to Dynamics 365 with retries and reconciliation checkpoints. |
| Mailchimp | Use constituent segments, consent information, and email engagement data for fundraising communications. | Blackbaud Raiser's Edge NXT → Martini → Mailchimp | Extract permitted Constituents and communication preferences, validate consent rules, transform audience fields, and synchronize approved segments to Mailchimp. Process engagement data in the reverse direction only where the selected APIs and data design support it. |
| Classy | Reconcile online fundraising, campaigns, and donor activity with Raiser's Edge NXT. | Classy → Martini → Blackbaud Raiser's Edge NXT | Receive or retrieve Classy fundraising data, match donors and campaigns using governed identifiers, map the result to SKY API-supported objects, and route unmatched or ambiguous records for review. |
| Blackbaud CRM | Coordinate enterprise fundraising and constituent data across Blackbaud fundraising products. | Blackbaud CRM → Martini → Blackbaud Raiser's Edge NXT | Use each product's supported API or export mechanism, establish system-of-record ownership, transform shared constituent and fundraising models, and reconcile changes through controlled scheduled workflows. |
| Luminate Online | Synchronize online engagement, forms, events, and fundraising activity with constituent records. | Luminate Online → Martini → Blackbaud Raiser's Edge NXT | Ingest supported Luminate Online data, resolve constituent identities, map event and fundraising fields to SKY API-supported operations, and persist checkpoints for incremental processing. |
| Blackbaud Tuition Management | Connect education-related payer or constituent information with institutional fundraising records where both products are used. | Blackbaud Tuition Management → Martini → Blackbaud Raiser's Edge NXT | Use a controlled data feed or supported APIs, validate payer and constituent matching, transform approved fields, and submit only operations available to the organization's SKY API permissions. |
| NetSuite | Transfer fundraising or financial settlement data into an ERP and support reconciliation. | Blackbaud Raiser's Edge NXT → Martini → NetSuite | Retrieve Gifts and related Funds, Campaigns, Appeals, and Constituents, normalize financial data, apply duplicate and reconciliation rules, and write approved transactions to NetSuite with checkpointed retries. |
How to build a Blackbaud Raiser's Edge NXT integration in Martini
Objective
Establish access to the organization's enabled Blackbaud SKY API products and permitted operations.
Instructions in Martini
- Register or use the approved Blackbaud application.
- Configure OAuth 2.0 client values, refresh tokens, and API subscription keys where required as Martini secrets.
- Confirm scopes, user permissions, organization context, and enabled product access.
- Use HTTPS and avoid exposing tokens or constituent data in logs.
Objective
Select an event-driven, scheduled, or API-led entry point based on the resource and completeness requirements.
Instructions in Martini
- Use a supported Blackbaud webhook notification when the required resource and event are covered.
- Use a scheduler for incremental polling, batch processing, or reconciliation.
- Expose a Martini API when another system needs to request Raiser's Edge NXT data or operations.
- Treat notifications as triggers to retrieve current data rather than complete business objects.
Objective
Call the appropriate SKY API resource and obtain the complete data required for processing.
Instructions in Martini
- Call the documented REST endpoint for Constituents, Gifts, Funds, Campaigns, Appeals, or Actions.
- Follow collection pagination until no further results remain.
- Retrieve related objects explicitly when Gift or campaign processing requires them.
- Persist a watermark, checkpoint, or source identifier for incremental synchronization.
Objective
Coordinate calls, transformations, conditions, and target operations in a maintainable Martini workflow.
Instructions in Martini
- Route responses by HTTP status, object type, and business outcome.
- Control concurrency for larger loads and throttling-sensitive operations.
- Separate successful records from validation and relationship exceptions.
- Use reusable workflow logic for token handling, pagination, matching, and target writes.
Objective
Convert SKY API objects into a canonical or target-specific model without losing source traceability.
Instructions in Martini
- Map Blackbaud identifiers to stable external keys.
- Normalize dates, timestamps, classifications, consent values, and financial amounts.
- Validate required fields and permitted relationships before writing.
- Apply organization-defined duplicate matching and field-ownership rules.
Objective
Perform controlled creates, updates, or publishes in downstream systems and preserve reconciliation references.
Instructions in Martini
- Use idempotent upserts where the target supports them.
- Store Blackbaud IDs and target IDs in a cross-reference model.
- Check for an existing financial transaction before retrying an ambiguous write.
- Transfer files or attachments only when the relevant SKY API resource supports them.
Common Blackbaud Raiser's Edge NXT data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Constituents | Individuals and organizations maintained in the constituent database, including contact details, preferences, and identifiers. | Salesforce, Microsoft Dynamics 365, Mailchimp, data warehouses | Martini retrieves or updates permitted fields, resolves identities using Blackbaud IDs and governed matching rules, and performs idempotent mappings. |
| Gifts | Donations and other gift transactions used for fundraising operations, reporting, and reconciliation. | NetSuite, analytics platforms, data warehouses, Microsoft Dynamics 365 | Martini retrieves Gifts with related objects, uses stable Gift identifiers for deduplication, and applies cautious retry logic for ambiguous write outcomes. |
| Funds | Fund classifications used to categorize or direct Gifts. | NetSuite, reporting platforms, analytics databases | Martini resolves Fund relationships, maps classifications to target hierarchies, and routes missing mappings for review. |
| Campaigns | Fundraising campaigns associated with Gifts and constituent activity. | Salesforce, Mailchimp, reporting platforms, analytics databases | Martini synchronizes campaign identifiers and classifications, applies target-specific transformations, and preserves source references. |
| Appeals | Fundraising appeals used to track solicitation activity and gift attribution. | Salesforce, Mailchimp, reporting platforms, analytics databases | Martini maps Appeals to target campaign structures, validates relationships, and handles ambiguous or missing classifications through exception routes. |
| Actions | Constituent-related tasks, interactions, or activities. | Salesforce, Microsoft Dynamics 365, reporting platforms | Martini retrieves supported Actions, transforms activity fields, applies business rules, and writes only to target operations permitted by the destination system. |
Authentication and security considerations
OAuth and application registration
Blackbaud SKY API applications generally use OAuth 2.0 with registered application credentials. Requests use bearer access tokens and may also require an API subscription key.
Least-privilege access
Scopes, authorizing-user permissions, enabled products, and Blackbaud organization context affect available operations. Configure only the permissions required by each workflow and test access against the target organization's environment.
Martini secrets and data protection
- Store OAuth client values, refresh tokens, subscription keys, and environment-specific values as Martini secrets.
- Use HTTPS and avoid logging access tokens, donor details, or unnecessary constituent attributes.
- Mask sensitive request and response fields and restrict access to workflows and operational logs.
Operational considerations for Blackbaud Raiser's Edge NXT integrations
Pagination and incremental synchronization
Collection endpoints should be paginated unless the resource documentation states otherwise. Use last-modified values where exposed, webhook notifications where supported, persisted watermarks, and periodic reconciliation.
Throttling and retries
Control concurrency and apply exponential backoff for throttling or transient failures. Large historical loads should use scheduled batches rather than unrestricted parallel requests.
Idempotency and relationships
Persist Blackbaud object IDs and use them as external keys. Gifts may require an existence check before retrying an ambiguous write. Resolve related Constituents, Funds, Campaigns, and Appeals explicitly.
Schema and notification changes
Webhook payloads may be incomplete and coverage is selective. Keep endpoint versions and mappings configurable, validate required fields, and monitor changes to fields, permissions, and resource behavior.
Testing and reconciliation
Test with the organization's actual enabled products, scopes, and permissions. Use scheduled reconciliation to detect missed notifications and verify target counts, relationships, and financial totals.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond point-to-point calls
Martini coordinates authentication, SKY API retrieval, pagination, related-object resolution, transformations, business rules, and downstream writes in maintainable workflows.
Reusable integration assets
Teams can expose controlled APIs, reuse workflow logic, centralize environment secrets, and create consistent mappings across Salesforce, Dynamics 365, reporting platforms, communications tools, and financial systems.
Operational reliability
- Persist checkpoints and cross-reference identifiers for resumable synchronization.
- Apply validation, idempotency, throttling controls, retries, and exception routing.
- Monitor workflow execution and distinguish authorization, validation, rate-limit, and target-system failures.
Frequently asked questions
Raiser's Edge NXT is primarily integrated through the Blackbaud SKY API, a REST-based platform. Applications can use OAuth 2.0, required application credentials and subscription keys, supported webhook notifications, scheduled pagination, controlled batches, and resource-specific file operations. Access depends on the organization's subscription, enabled products, application registration, scopes, and user permissions.
Yes. Martini can consume the Blackbaud SKY API, handle OAuth-based authentication and required headers, receive selected webhook notifications, orchestrate scheduled or event-driven workflows, map Raiser's Edge NXT objects, and expose normalized APIs to downstream systems. The available operations depend on the organization's SKY API access.
No. A dedicated Blackbaud Raiser's Edge NXT connector is not required. Martini can integrate using the confirmed Blackbaud SKY API REST interface, OAuth 2.0, API subscription keys where required, selected webhook notifications, and resource-specific file or attachment endpoints.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Blackbaud Raiser's Edge NXT. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Blackbaud, cloud infrastructure, or other third-party systems based on subscriptions, usage, and deployment model.
The documented primary method is the Blackbaud SKY API REST interface. Selected resources and events also support webhook-style notifications, while larger workloads can use pagination, scheduled incremental polling, controlled batches, and checkpoints. GraphQL and SOAP were not confirmed as official recommended SKY API methods, and direct database access is not a supported standard approach.
Yes, but only for selected supported resources and events. Webhook coverage is not universal, payloads may not contain the complete business object, and subscription requirements vary. A robust Martini design validates the notification, retrieves the current object through the SKY API, and supplements event processing with scheduled reconciliation.
Martini can use stable Blackbaud object identifiers, persisted checkpoints or watermarks, pagination, and idempotent target upserts. Gifts require particular care: after an ambiguous failure, the workflow should check whether the target transaction already exists before retrying. Matching should not rely solely on names or email addresses.
Martini workflows can transform Constituents, Gifts, Funds, Campaigns, Appeals, and Actions into canonical or target models, validate required relationships, route exceptions, and retry transient failures. They can also limit concurrency, apply backoff for throttling responses, persist checkpoints, and monitor failed mappings or API-version changes.
Yes. Martini can expose a controlled REST API that hides SKY API authentication and implementation details from internal applications. The façade can normalize Raiser's Edge NXT objects, enforce authorization and business rules, orchestrate multiple API calls, and provide a stable internal contract while the underlying workflow manages pagination, retries, and permissions.
Related Martini documentation
API Workflows
Mapping
Integrate Blackbaud Raiser's Edge NXT with confidence
Use Martini to connect the Blackbaud SKY API with your fundraising, CRM, communications, finance, and reporting landscape through secure, maintainable workflows.