Ellipse Gradient for Header

Blackbaud Financial Edge NXT Integration Guide

Integrate Financial Edge NXT with enterprise applications through the Blackbaud SKY REST API, OAuth 2.0, selected webhook notifications, and scheduled workflows.

Blackbaud Financial Edge NXT integration options at a glance

Financial Edge NXT uses the Blackbaud SKY API as its primary integration surface, providing REST endpoints for financial resources such as Accounts, Funds, Projects, Vendors, Invoices, and journal-related objects. Applications authenticate with OAuth 2.0 bearer tokens, refresh tokens, scopes, tenant authorization, and a Blackbaud API subscription key. SKY API webhook-style notifications are available for selected products and events, but coverage varies by resource. Martini can consume the REST API, receive supported notifications, run scheduled incremental synchronizations, paginate high-volume requests, transform financial data, and expose controlled APIs for downstream applications. Bulk, attachment, and batch capabilities should be verified for each endpoint.

Integration pointSupported by Blackbaud Financial Edge NXT?Common use casesHow Martini supports it
Blackbaud SKY REST APIsYesRead and, where supported by the resource and permissions, create or update Accounts, Funds, Projects, Vendors, Invoices, journal-related objects, Purchase Orders, and Grants.Martini consumes REST endpoints from workflows, handles request orchestration and pagination, maps responses, applies business rules, and can expose a controlled API façade.
Webhooks and outbound callbacksLimitedReceive notifications for selected products and events within the SKY API ecosystem. Coverage is resource- and product-dependent.Martini can receive supported notifications through an API or webhook-triggered workflow, retrieve current state, deduplicate events, and supplement them with scheduled reconciliation.
OAuth 2.0 and API subscription keysYesAuthenticate applications with OAuth access and refresh tokens, requested scopes, tenant authorization, Blackbaud permissions, and the Bb-Api-Subscription-Key header.Martini stores client credentials, refresh tokens, and subscription keys in environment configuration or secrets and uses them in API workflows.
Bulk, asynchronous, and batch processingLimitedFinancial Edge NXT includes batch-oriented concepts such as journal entry batches, but a universal bulk or asynchronous API is not confirmed for every resource.Martini can orchestrate paginated and bounded batch processing, maintain checkpoints, and apply retry and backoff logic after resource-level verification.
File and attachment APIsLimitedDocument or attachment capabilities may be available for selected resources, but a universal file API was not confirmed.Martini can handle files when the specific SKY endpoint supports them, while keeping file mappings and transfer logic resource-specific.
Scheduled synchronizationYesPoll REST endpoints when event coverage is unavailable, using modification timestamps, object identifiers, reconciliation windows, or other documented incremental fields.Martini scheduler-triggered workflows retrieve pages, transform data, persist watermarks, and restart from durable checkpoints.
Direct database accessNot confirmedDirect customer access to the Blackbaud-hosted Financial Edge NXT database is not confirmed and should not be assumed.Martini should use the documented SKY API or other officially supported Blackbaud mechanisms rather than a JDBC connection to the SaaS database.

How Blackbaud Financial Edge NXT exposes data and business events

Blackbaud SKY REST APIs

The Blackbaud SKY API is the primary documented integration surface for Financial Edge NXT. Its product-specific REST endpoints expose financial resources, with available operations, fields, versions, and permissions varying by resource and organization configuration.

Martini implementation pattern

Martini authenticates to the SKY API, invokes the required resource endpoints, follows pagination, transforms responses into canonical or target-specific models, applies financial validation rules, and writes results to downstream systems. API errors are classified for retry, correction, or escalation.

Implementation sequence

Authenticate with an OAuth access token and API subscription key
Invoke the documented Financial Edge NXT resource endpoint
Retrieve all result pages and preserve the source identifiers
Map the response into a canonical or target model
Validate accounts, funds, projects, dates, and monetary values
Write the result to the downstream system and store the checkpoint

SKY API webhook-style notifications

Blackbaud provides webhook-style notifications for selected products and events in portions of the SKY API ecosystem. Coverage is not universal for every Financial Edge NXT object or operation, so each event use case requires endpoint-level verification.

Martini implementation pattern

Martini exposes a receiving API or webhook-triggered workflow for a supported notification, validates its authenticity and contents where documented, retrieves the current Financial Edge NXT object, and routes the resulting state to downstream systems. Scheduled reconciliation protects against missed or delayed events.

Implementation sequence

Receive the supported Blackbaud notification
Validate the event and identify the affected resource
Retrieve the current Financial Edge NXT object
Deduplicate using the event or object identifier
Map and route the current state to downstream systems
Record the outcome and reconcile periodically

Scheduled Financial Edge NXT synchronization

Scheduled polling is appropriate when a required object does not have suitable event coverage or when a periodic completeness check is needed. Incremental synchronization should use documented modification fields, identifiers, or a reconciliation window.

Martini implementation pattern

A Martini scheduler-triggered workflow reads its stored watermark, requests paginated SKY API data, transforms and validates each page, writes results idempotently, and persists progress only after successful processing. Controlled retries and bounded concurrency reduce rate-limit and restart risks.

Implementation sequence

Start the scheduled synchronization workflow
Read the last successful watermark or reconciliation window
Request the next paginated SKY API result
Transform and validate each Financial Edge NXT object
Upsert the result and record source identifiers
Persist the checkpoint and report failures for retry

Common Blackbaud Financial Edge NXT integration patterns

Pattern 1: Synchronize Financial Edge NXT finance data to a warehouse

When to use this pattern

Use this pattern when reporting teams need Accounts, Funds, Projects, Vendors, and financial activity without granting every analytics consumer direct access to Financial Edge NXT. A scheduled incremental process provides repeatability and a durable audit trail.

Integration direction
Blackbaud Financial Edge NXT
Martini
Data warehouse
Example Mapping
Blackbaud Financial Edge NXT FieldCanonical FieldTarget Field
account_numberaccountCodeaccount_code
fund_idfundIdentifierfund_id
project_idprojectIdentifierproject_id
modified_datesourceModifiedAtsource_modified_at
Martini implementation pattern

Martini authenticates to the SKY API, retrieves pages using an incremental watermark, converts exact monetary values and dates into the warehouse model, validates references, and writes idempotently. Checkpoints are committed after successful batches, while throttling, transient errors, and rejected rows are handled separately.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination and checkpoints
  • data mapping
  • business rules
  • error handling

Pattern 2: Synchronize accounts payable with NetSuite

When to use this pattern

Use this pattern when Vendors, Invoices, Purchase Orders, or related financial information must move between Financial Edge NXT and NetSuite during coexistence or consolidation. Duplicate prevention and financial reference validation are essential.

Integration direction
Blackbaud Financial Edge NXT
Martini
NetSuite
Example Mapping
Blackbaud Financial Edge NXT FieldCanonical FieldTarget Field
vendor_idsupplierExternalIdvendor.externalId
invoice_numberinvoiceReferenceinvoice.tranId
fund_idfundReferenceinvoice.customFund
amountinvoiceAmountinvoice.total
Martini implementation pattern

Martini retrieves or receives approved source data, validates account, fund, and project references, checks stable vendor and invoice identifiers, and submits the target API request. The workflow records target identifiers, distinguishes validation from transient failures, and retries only safe operations.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • validation
  • idempotent processing
  • retry handling

Pattern 3: Route finance approvals from ServiceNow

When to use this pattern

Use this pattern when finance requests, vendor onboarding, or approvals originate in ServiceNow but approved transactions must be processed through Financial Edge NXT. The workflow should not treat an HTTP acceptance response as proof of completed accounting posting.

Integration direction
ServiceNow
Martini
Blackbaud Financial Edge NXT
Example Mapping
Blackbaud Financial Edge NXT FieldCanonical FieldTarget Field
requested_vendorvendorReferenceVendors.id
requested_fundfundReferenceFunds.id
requested_projectprojectReferenceProjects.id
approval_statusworkflowDecisionfinancialOperation
Martini implementation pattern

Martini receives the approved request, validates required references and monetary precision, calls the supported SKY API operation, stores the Financial Edge NXT identifier and state, and updates ServiceNow. Pending, rejected, and posted states are reconciled through follow-up workflows.

Martini capabilities used
  • API-triggered workflows
  • business rules
  • data transformation
  • orchestration
  • state tracking
  • error handling

Pattern 4: Use event-assisted financial updates with reconciliation

When to use this pattern

Use this pattern when a relevant SKY API notification is available for a Financial Edge NXT resource but delivery may be incomplete or event coverage may change. It combines low-latency processing with scheduled completeness checks.

Integration direction
Blackbaud Financial Edge NXT
Martini
Salesforce
Example Mapping
Blackbaud Financial Edge NXT FieldCanonical FieldTarget Field
object_idsourceObjectIdexternalFinancialId
modified_datesourceModifiedAtlastFinancialUpdate
statusfinancialStatusaccountingStatus
fund_idfundReferencefundCode
Martini implementation pattern

Martini receives the supported notification, validates and deduplicates it, retrieves current state from the SKY API, and maps that state to Salesforce. A scheduled reconciliation workflow compares recent changes and reprocesses missed or delayed notifications without creating duplicates.

Martini capabilities used
  • webhook-triggered workflows
  • API consumption
  • data mapping
  • deduplication
  • scheduled reconciliation
  • monitoring

Applications commonly integrated with Blackbaud Financial Edge NXT

Financial Edge NXT can be integrated with adjacent business applications when organizations need to coordinate accounting, procurement, operational workflows, reporting, or approvals. The exact direction and object coverage depend on the products deployed, system-of-record decisions, and the permissions available to the SKY API application.

Application Scenario Direction Martini Pattern
Salesforce Synchronize approved fundraising or constituent-related financial outcomes with accounting data and status information. Salesforce → Martini → Blackbaud Financial Edge NXT Martini receives approved Salesforce transactions or financial references, validates account, fund, and project mappings, and submits supported Financial Edge NXT API requests. Posted or rejected status can be returned to Salesforce through a separate workflow.
Microsoft Dynamics 365 Coordinate finance, procurement, vendor, and operational information when Microsoft business applications coexist with Financial Edge NXT. Microsoft Dynamics 365 → Martini → Blackbaud Financial Edge NXT Martini consumes source-system changes, applies organization-specific coding and duplicate rules, and orchestrates Financial Edge NXT REST calls. Reconciliation workflows return processing status and API errors to the originating application.
NetSuite Exchange vendors, invoices, journal activity, funds, and reporting dimensions during coexistence or financial consolidation projects. Blackbaud Financial Edge NXT → Martini → NetSuite Martini retrieves paginated SKY API resources, maps them to NetSuite objects, preserves stable source identifiers, and performs idempotent create-or-update processing with checkpoints and retry handling.
Workday Coordinate supplier, procurement, workforce-related, or finance data with nonprofit accounting processes. Workday → Martini → Blackbaud Financial Edge NXT Martini validates Workday-originated reference data against Financial Edge NXT Accounts, Funds, and Projects before submitting supported transactions, then exposes outcome data for downstream reporting.
ServiceNow Support controlled workflows for finance requests, vendor onboarding, approvals, and service operations. ServiceNow → Martini → Blackbaud Financial Edge NXT A ServiceNow request starts a Martini workflow that validates business rules and reference data, calls supported SKY API endpoints, records the Financial Edge NXT identifier, and updates the request with processing status.
Jira Link implementation tasks, finance-related requests, or grant and project work with selected financial status and budget information. Jira → Martini → Blackbaud Financial Edge NXT Martini translates approved Jira project metadata into Financial Edge NXT Projects or related references where the API supports the operation, and synchronizes selected status information back using scheduled workflows.
Microsoft Power BI Provide reporting based on synchronized Accounts, Funds, Projects, Vendors, and journal information without giving every analytics consumer direct API access. Blackbaud Financial Edge NXT → Martini → Microsoft Power BI Martini performs scheduled, paginated extraction from the SKY API, maps data to a reporting schema, writes it to an approved data store or reporting ingestion surface, and records watermarks for incremental refreshes.
DocuSign Connect invoice, vendor, or approval processes with electronic signature workflows. Blackbaud Financial Edge NXT → Martini → DocuSign Martini sends eligible approval information to DocuSign through its API and routes signed or rejected status back to the originating workflow or Financial Edge NXT endpoint where the required operation is supported.

How to build a Blackbaud Financial Edge NXT integration in Martini

Objective

Establish the SKY API connection using the organization’s authorized Blackbaud application and environment-specific credentials.

Instructions in Martini

  • Register or use the authorized Blackbaud application.
  • Configure OAuth 2.0 client settings, refresh tokens, scopes, tenant authorization, and the API subscription key.
  • Store credentials and subscription keys in Martini secrets or environment configuration.
  • Separate development, testing, and production configuration.

Objective

Select an event-assisted, API-triggered, or scheduled entry point based on the resource’s confirmed integration coverage.

Instructions in Martini

  • Use a supported Blackbaud notification when relevant coverage is confirmed.
  • Use a Martini API when another application initiates the process.
  • Use a scheduler for polling, incremental synchronization, and reconciliation.
  • Define a watermark or durable processing key before extracting data.

Objective

Call the documented SKY API endpoints and obtain complete, current resource data rather than relying on incomplete notifications.

Instructions in Martini

  • Request the required Financial Edge NXT resource.
  • Follow pagination until the API indicates that no pages remain.
  • Retrieve current state after a webhook-style notification.
  • Capture source identifiers, API versions, response status, and correlation context.

Objective

Coordinate validation, transformation, target calls, checkpoints, and exception paths in a maintainable Martini workflow.

Instructions in Martini

  • Separate authentication, retrieval, mapping, business rules, target writes, and reconciliation steps.
  • Use bounded concurrency for high-volume processing.
  • Persist progress after successful units of work.
  • Route authentication, authorization, throttling, validation, and downstream failures differently.

Objective

Convert Financial Edge NXT objects into canonical or target-specific models while protecting accounting integrity.

Instructions in Martini

  • Map Accounts, Funds, Projects, Vendors, Invoices, and journal-related fields explicitly.
  • Validate account, fund, project, date, status, and monetary-value rules.
  • Use exact decimal handling for financial amounts.
  • Allow optional fields while handling new enum values explicitly.

Objective

Submit safe target operations and make processing state visible to connected applications and operators.

Instructions in Martini

  • Use create-or-update behavior based on stable identifiers or documented business keys.
  • Record target identifiers and Financial Edge NXT state transitions.
  • Do not equate HTTP acceptance with completed posting or approval.
  • Run reconciliation for pending, rejected, delayed, or missed transactions.

Common Blackbaud Financial Edge NXT data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
AccountsSynchronize general ledger accounts, classifications, and accounting references.Data warehouses, NetSuite, Microsoft Dynamics 365, Power BIMartini retrieves account data through documented SKY API endpoints, validates mappings, and preserves stable identifiers for downstream references.
FundsClassify and report on nonprofit financial activity by fund.Data warehouses, reporting platforms, Salesforce, Power BIMartini maps fund codes and descriptions to canonical reporting dimensions and applies organization-specific validation rules.
ProjectsTrack project, grant-related, or program financial structures.Jira, Workday, reporting platforms, data warehousesMartini synchronizes supported project fields, combines or translates dimensions when required, and maintains source-to-target references.
VendorsManage supplier and payee information for procurement and accounts payable processes.NetSuite, Workday, Microsoft Dynamics 365, ServiceNowMartini validates vendor identifiers, applies duplicate detection, and routes approved create-or-update operations to target APIs.
InvoicesExchange accounts payable invoices and related financial information.NetSuite, Microsoft Dynamics 365, ServiceNow, DocuSignMartini validates account, fund, and project references, applies idempotent processing, and distinguishes accepted, rejected, pending, and posted states where available.
Journal entriesSynchronize general ledger journal activity and journal entry batches.NetSuite, data warehouses, Power BI, Microsoft Dynamics 365Martini handles journal-related API operations according to endpoint permissions and state rules, records batch identifiers, and reconciles processing outcomes.

Authentication and security considerations

OAuth 2.0 and subscription keys

Financial Edge NXT integrations use the Blackbaud SKY API authentication model. Applications obtain OAuth 2.0 access tokens and send bearer tokens with requests, together with the Blackbaud API subscription key.

Scopes and tenant permissions

Access depends on requested scopes, tenant authorization, and the Blackbaud user or application permissions for the requested Financial Edge NXT resources. A valid token does not guarantee access to every endpoint.

Secrets and least privilege

Store OAuth client credentials, refresh tokens, and subscription keys in Martini environment configuration or secrets. Request only the scopes required by the workflows and keep development, testing, and production credentials separate.

Operational considerations for Blackbaud Financial Edge NXT integrations

Pagination and rate limits

Design collection workflows to follow pagination until completion. Use bounded concurrency, controlled retries, and backoff for throttling or transient service responses.

Idempotency and checkpoints

Use stable Blackbaud identifiers, invoice numbers, journal batch identifiers, or documented business keys to prevent duplicates. Persist checkpoints after successful batches so a retry does not restart the entire extraction.

Financial integrity

Validate account, fund, project, date, status, and monetary fields before posting or forwarding data. Use exact decimal handling and distinguish submitted, pending, rejected, and posted states.

Schema and event changes

Review SKY API versions and Blackbaud release information before changing mappings. Treat webhook notifications as triggers to retrieve current state, and supplement them with periodic reconciliation because event coverage is partial.

Testing and observability

Test authentication, permission failures, pagination, rate limiting, duplicate delivery, optional fields, and downstream rejection paths. Log endpoint, API version, object type, source identifier, correlation ID, retry count, and error classification without exposing secrets.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration instead of isolated scripts

Martini provides a maintainable workflow for authentication, paginated SKY API consumption, transformation, validation, target writes, retries, reconciliation, and monitoring. Integration logic remains visible and reusable rather than being distributed across unrelated scripts.

Controlled APIs and reusable models

Martini can expose a controlled API façade that shields downstream applications from Blackbaud-specific authentication, pagination, resource models, and version details. It can also normalize Accounts, Funds, Projects, Vendors, Invoices, and journal-related data for multiple consumers.

Reliable enterprise processing

Scheduled workflows, event-assisted processing, checkpoints, idempotency rules, and differentiated error handling support reliable financial synchronization. Martini can apply organization-specific business rules without requiring direct database access to the Financial Edge NXT SaaS application.

Frequently asked questions

How can Blackbaud Financial Edge NXT be integrated with enterprise systems?

Financial Edge NXT is integrated primarily through the Blackbaud SKY API, which provides product-specific REST endpoints. Applications authenticate with OAuth 2.0, bearer access tokens, required scopes, tenant authorization, Blackbaud permissions, and an API subscription key. Selected SKY API products and events also support webhook-style notifications, while scheduled polling is appropriate when event coverage is unavailable or incomplete.

Can Martini integrate with Blackbaud Financial Edge NXT?

Yes. Martini can consume the Blackbaud SKY REST API, manage OAuth-based authentication and subscription-key configuration, receive supported webhook-style notifications, run scheduled synchronization workflows, map and validate financial data, and expose controlled APIs for downstream applications.

Do I need a connector to integrate Blackbaud Financial Edge NXT with Martini?

No. A dedicated Blackbaud Financial Edge NXT connector is not required. Martini can integrate using the confirmed native SKY REST API, supported webhook-style notifications, OAuth 2.0, API subscription keys, and scheduled workflow patterns.

Is there any extra Lonti cost to integrate Blackbaud Financial Edge NXT with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Blackbaud Financial 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 depending on subscriptions, usage, and deployment model.

Which Blackbaud Financial Edge NXT integration methods should be used?

The Blackbaud SKY REST API is the primary and recommended integration method. OAuth 2.0 and the API subscription key support authentication. Webhook-style notifications can be used for selected events after resource-level verification, while scheduled REST synchronization provides coverage where notifications are unavailable. A current Financial Edge NXT GraphQL or SOAP API was not confirmed.

Are webhooks or events available for Financial Edge NXT?

Blackbaud provides webhook-style capabilities for selected products and events within the SKY API ecosystem, but coverage is product- and resource-dependent. Martini can receive applicable notifications, retrieve current object state, deduplicate processing, and use scheduled reconciliation to address delayed or missed events.

How does synchronization and data mapping work?

Martini can retrieve paginated Accounts, Funds, Projects, Vendors, Invoices, journal-related objects, Purchase Orders, or Grants through documented SKY API endpoints. It maps those objects to canonical or target models, validates financial references and exact monetary values, uses stable identifiers for idempotency, and stores watermarks or checkpoints for incremental processing.

How are errors, retries, and duplicate financial transactions handled?

Workflows should distinguish authentication, authorization, throttling, validation, and downstream failures. Martini can apply controlled retries and backoff for transient errors, persist checkpoints, use source identifiers or business keys for duplicate detection, and reconcile pending or rejected financial operations rather than assuming that a successful HTTP response means posting is complete.

Related Martini documentation

API Workflows

Workflows

Security

Reliability

Connect Blackbaud Financial Edge NXT with Martini

Use Martini to build secure, observable Financial Edge NXT integrations around the Blackbaud SKY API, selected event notifications, and scheduled financial workflows.

EXPLORE MARTINI
BOOK A DEMO