Blackbaud SKY API

Raiser's Edge NXT integration for UK charities

We connect Raiser's Edge NXT to the systems around it. Online gifts recorded within minutes with their Gift Aid declarations, thank-yous triggered from new gifts, and data exported where Raiser's Edge has no export. We have delivered three pieces of Raiser's Edge NXT work for UK charities, two of them running every day.

Campaign report in the With Thanks portal, a charity platform we built that syncs gifts from Raiser's Edge NXT

What we connect to Raiser's Edge NXT

Work we have delivered through the Blackbaud SKY API, not a list of things we would like to try.

Online giving platforms

Each online donation is captured as it happens, matched to the right supporter and written as a gift with the agreed fund, campaign and appeal. We run this in production between iRaiser and Raiser’s Edge NXT.

Gift Aid declarations

When a donor opts in on the form, the declaration is written to their record in the same run as the gift, so declarations are no longer typed in by hand.

Regular giving

Monthly payments are attached to the supporter’s existing recurring gift, not entered as unrelated one-off donations.

Thank-yous and stewardship

The With Thanks portal reads qualifying new gifts from Raiser’s Edge NXT every hour, sends each donor a personalised thank-you video and writes the acknowledgement back to the gift.

Exports Raiser’s Edge does not offer

There is no bulk export for attachments. We wrote a read-only tool that checked 60,236 supporter records and exported 63,200 files, each with a checksum and a manifest row.

Exceptions for people, not guesses

Anything uncertain, such as two possible donor matches or a gift already keyed by hand, is held and listed in a daily email that contains no donor personal data.

Online donations recorded within minutes

A UK children's charity, live since October 2026

The charity took online donations through iRaiser and keyed every one into Raiser's Edge NXT by hand. Two n8n workflows now do it through the SKY API: gifts appear in the CRM within minutes, Gift Aid declarations are written for donors who opted in, and nothing is re-keyed. Volumes are modest, so the benefit is accuracy and speed, not scale.

Read the donations sync case study, or our guide tosyncing online donations into Raiser's Edge NXT.

Capture first, process second

An authenticated webhook acknowledges each donation at once and logs the raw delivery. A separate workflow does the matching and writing, so a processing problem never loses a donation.

Safe to repeat

A sync log keyed on the donation reference means a repeated delivery is recognised and skipped. The same log is the record of what has been written to the CRM.

Matching without guessing

Email address first, then surname and postcode. One match is used, none creates a new constituent, and several possible matches are held for a person to decide.

63,200 attachments exported in under seven hours

The same charity held scanned records, mainly Gift Aid declaration scans, as attachments on supporter records, and Raiser's Edge NXT has no bulk export for them. We ran the export on 28 October 2026, delivered the files by SFTP and permanently deleted our working copy once the charity confirmed receipt. Read the attachments export case study, or our guide to exporting attachments from Raiser's Edge NXT.

60,236
Supporter records checked
63,200
Files exported
15.9 GB
Total size
6h 43m
Run time
Nothing written to the CRM

The tool uses GET requests only. Requests are paced, and when the API asks it to wait, it waits for exactly as long as it is told.

Resumable

Each finished supporter record goes on a done-list. When a Blackbaud error stopped the full run part-way, restarting picked up where it had stopped.

Every file accounted for

Download links expire after 30 minutes, so each file is fetched straight after it is listed. Every file gets a SHA-256 digest and a manifest row; anything without a file is listed separately.

How an integration project runs

Small steps, with nothing written to your live database until you have seen what would be written.

Mapping call

We go through the flow with the person who does it by hand today: which fund, campaign and appeal a gift gets, how donors are matched, and what your team does with the awkward cases.

Read first

Once your administrator approves the application, we read your code tables and a sample of existing records, so the integration follows your conventions instead of inventing its own.

Dry run

The integration processes real inputs and reports what it would write, without writing it. You compare that with what your team entered for the same gifts.

Supervised go-live

The first live records are checked together. We agree a cutover point so the same gift is not entered both by hand and by the integration.

Monitoring

Failures raise an alert, and a daily email lists only the items that need a person. We stay on a retainer or hand over, as you prefer.

Raiser's Edge NXT integration FAQs

The questions fundraising and data teams ask us before starting.

How much does a Raiser's Edge NXT integration cost?

It depends on how many record types are involved, how donors are matched and how much needs a person to review. A single flow, such as online gifts into Raiser's Edge NXT, is a small project; a platform that reads and writes several record types is larger. Every engagement is scoped and fixed-priced after a short discovery. See our pricing page for how we price.

Do you need to be given a login to our Raiser's Edge database?

An integration connects through the Blackbaud SKY API using an application that your Raiser’s Edge NXT administrator approves. The application only gets the access it is granted, and your administrator can remove it at any time. During the build we usually also need a named user account so we can see records the way your team does.

Will an integration create duplicate supporters?

Not if it is built to hold what it cannot decide. Our online donations sync matches a donor by email address first, then by surname and postcode. One match is used, no match creates a new constituent, and more than one possible match is held for a person to choose. It also checks whether the gift has already been entered by hand before writing anything.

Can you write Gift Aid declarations as well as gifts?

Yes. Where the donor opted in on the giving form, the declaration is written against their record in the same run as the gift, with the declaration source and method your team already uses, so nothing has to be typed in later.

What happens when Blackbaud limits the number of API calls?

The SKY API allows a set number of calls a second and a daily quota that depends on your subscription tier. We design for both: requests are paced, a refused call is retried after the wait Blackbaud asks for, and long jobs keep a record of what is finished so they can resume. Our guide to SKY API rate limits and quotas explains the detail.

Which fundraising platforms can you connect?

We have connected iRaiser to Raiser’s Edge NXT in production, and built a thank-you video platform that reads gifts from Raiser’s Edge NXT and Salesforce NPSP. Any platform that can send a webhook or offers an API or a scheduled export can be connected in the same way. If yours cannot do any of those, we will tell you before any work starts.

Who looks after the integration once it is live?

We can run it on a monthly retainer covering monitoring, Blackbaud API changes and small adjustments, or hand it over with documentation to your own team. Either way the workflows, the code and the accounts they run in are yours.

Still re-keying data into Raiser's Edge?

Tell us which two systems do not talk to each other; we respond within one working day. If it cannot be done reliably, we will say so.