· Vimal Hari · Business Automation (n8n) · 6 min read

How to Bulk Export Attachments from Raiser's Edge NXT

Raiser's Edge NXT has no bulk export for attachments. Here is how to get every file out through the SKY API, safely and with proof that the copy is complete.

Raiser's Edge NXT has no bulk export for attachments. Here is how to get every file out through the SKY API, safely and with proof that the copy is complete.

Raiser’s Edge NXT lets you open an attachment on a supporter record, and it lets you download it. What it does not offer is a way to take all of them at once. If your charity keeps scanned Gift Aid declarations, letters or signed forms as attachments and you want your own complete copy, there is no button for that.

We met this in October 2026, when a UK children’s charity asked us for an offline copy of its scanned records. The export covered 60,236 supporter records and produced 63,200 files, 15.9 GB in all, in 6 hours 43 minutes. This guide explains how it works, what the Blackbaud SKY API will and will not give you, and the checks that let you say the copy is complete. The full write-up is in our attachments export case study.

Why there is no simple answer

Three facts shape the whole job.

  • There is no bulk attachment endpoint. The SKY API has nothing that lists attachments across the database. You ask for the attachments of one record at a time.
  • Download links expire. For a file stored in Raiser’s Edge, the API returns a url that is only valid for 30 minutes. A script that lists everything first and downloads later will find its early links dead.
  • Every listing costs an API call. One call per supporter record, whether or not that record has any attachments. The number of calls is set by the size of your database, not by the number of files.

What the API gives you

Attachments hang off the record they belong to, and each record type has its own endpoint:

RecordEndpoint
ConstituentGET /constituent/v1/constituents/{constituent_id}/attachments
GiftGET /gift/v1/gifts/{gift_id}/attachments
ActionGET /constituent/v1/actions/{action_id}/attachments

The constituent endpoint has no paging and no filter by tag or date. It returns every attachment on that record, each with an id, a type, a name, a date, a file_name, a content_type, any tags, and for stored files a url.

The type matters. A Physical attachment is a file held by Blackbaud, which you can download. A Link attachment is only a web address someone pasted in; there is no file to export, and the address may point at a shared drive that no longer exists. A file that Blackbaud has quarantined comes back with its details but no url. Record both cases in your results; neither is a failure of the export.

To walk the whole database you first need the list of constituent IDs:

GET /constituent/v1/constituents?limit=5000&include_deceased=true&include_inactive=true&fields=id

Two details here are easy to miss. Results come up to 5,000 at a time, with a next_link to the following page. And deceased and inactive records are left out unless you ask for both. If your scans date from years ago, a large share of them will sit on exactly those records, so an export without the two flags looks complete and is not.

Count the calls before you start

The SKY API applies two limits, which Blackbaud documents under rate limits and quotas: 10 calls a second, and a daily quota that depends on your subscription tier and resets at 00:00 UTC.

TierDaily quotaWho can have it
Free1,000 callsAnyone
Standard25,000 callsCustomers and Blackbaud Partners
Partner100,000 per connectionBlackbaud Partners

For a database of 60,000 supporter records that is 60,000 listing calls plus a few for the ID pages. On the Free tier it would take two months. On Standard it takes three days. Standard is not automatic: a developer has to join your organisation’s SKY Developer team and claim the upgrade. Settle this with your Raiser’s Edge administrator before anything else. Our guide to SKY API rate limits and quotas covers the tiers in more detail.

If you only need some records, the constituents endpoint accepts a list_id, so a saved list in Raiser’s Edge can cut the run down to the supporters you care about.

How we built the export

The tool is a small Python program. Its design follows from the constraints above.

  1. Read only. It makes GET requests and nothing else, and the application is registered with read access only. Nothing it does can change a record.
  2. Paced, and polite when refused. Requests are throttled below the rate limit. When the API answers 429, the tool waits for the number of seconds in the Retry-After header and tries again.
  3. Download straight after listing. For each record it lists the attachments and fetches the files at once, well inside the 30 minutes.
  4. Resumable. Each finished record is written to a done-list. On our full run a Blackbaud 502 stopped the tool part-way through; restarting it carried on from where it had stopped.
  5. A pilot first. We ran a few dozen records before the full export, which showed what the files were and gave us a sound estimate for the whole run.

The core loop is short:

for constituent_id in remaining_ids:
    items = get(f"/constituent/v1/constituents/{constituent_id}/attachments")["value"]
    for item in items:
        if item["type"] != "Physical" or not item.get("url"):
            exceptions.append(item)      # link only, or no file to fetch
            continue
        data = download(item["url"])     # the link is valid for 30 minutes
        save(constituent_id, item, data)
        manifest.append(row(constituent_id, item, sha256(data)))
    mark_done(constituent_id)

get adds the Authorization and Bb-Api-Subscription-Key headers and handles the 429 wait.

Proving the copy is complete

An export you cannot check is not worth much, least of all when the files are the evidence behind Gift Aid claims. We deliver three things alongside the files.

  • A manifest. One row per file: the supporter record, the attachment ID, the original file name, the date on the attachment, its tags, its size and a SHA-256 digest. Anyone can recompute the digest later to confirm that a file has not changed.
  • An exceptions list. Every item that is a link only, has no file, or failed to download, with the reason. A short, explained list is far more reassuring than a claim of perfection.
  • A summary. Records checked, records with attachments, files and total size, so the numbers can be compared with what your team expects.

Do not filter by the attachment’s date. That field is typed in by whoever added the file, and it is often blank or wrong. Take every file and record the date in the manifest, so the sorting can be done afterwards without losing anything.

Handing it over

The files are personal data. We delivered them by SFTP, the charity confirmed receipt the next day, and we then permanently deleted our working copy so that we held no more of its data than we needed. Agree that plan, and who signs it off, before the export runs.

When you need a developer

If your database is small and you only need a handful of records, downloading by hand is quicker than any of this. Past a few hundred files it stops being practical, and the cost of a missed record goes up.

This is work we do: see Raiser’s Edge NXT integration for the other ways we connect Raiser’s Edge to the systems around it, or get in touch and tell us what you need to get out.

Back to Blog

Related Posts

View All Posts »