· Vimal Hari · Business Automation (n8n) · 6 min read
Blackbaud SKY API Rate Limits and Quotas Explained
The SKY API allows 10 calls a second and a daily quota set by your tier. What each tier gives you, what the two errors mean, and how to design within them.

Every integration with Raiser’s Edge NXT goes through the Blackbaud SKY API, and the SKY API limits how often you can call it. The limits decide whether a job takes an afternoon or a fortnight, and they are the usual reason an integration that passed its tests fails in its first busy week.
This guide covers the two limits, what each subscription tier allows, and how we design within them. The figures are from Blackbaud’s documentation as it stood on 16 November 2026; Blackbaud says they can change without notice, so check the rate limits and quotas and subscription tiers pages before you plan around them.
Two limits, two different errors
The rate limit is 10 calls a second. It protects Blackbaud’s servers from short bursts. Go over it and the API answers 429 Too Many Requests with a Retry-After header giving the number of seconds to wait, usually one.
The quota is a number of calls a day. It caps sustained use, and it resets at 00:00 UTC, not 24 hours after your first call. Go over it and the API answers 403 with the message “Out of call volume quota” and a Retry-After header that tells you how long until the reset.
The two need opposite responses. A 429 means wait a second and carry on. A quota 403 means stop until tomorrow; retrying in a loop achieves nothing. Code that treats every 403 as a permissions problem will send you looking in the wrong place.
One more thing to know: a successful response does not tell you how much quota is left. You find the ceiling in the developer portal, and you find the edge by hitting it.
What each tier allows
| Tier | Daily quota | Who can have it |
|---|---|---|
| Free | 1,000 calls, in total | Anyone |
| Standard | 25,000 calls, in total | Customers and Blackbaud Partners |
| High volume | 100,000 calls, in total | Customers, for $5,000 a year |
| Max volume | 250,000 calls, in total | Customers, for $10,000 a year |
| Partner | 100,000 calls per connection | Blackbaud Partners |
“In total” means the quota is shared across everything that developer account’s subscription does. “Per connection” means each charity that connects a partner’s application gets its own 100,000, which is what lets a product serve many charities.
Three points catch people out.
- The quota belongs to the developer, not to the charity. The calls are counted against the subscription key of whoever built the application. Connecting to a large charity does not lend you its allowance.
- Standard is not automatic. A developer starts on Free. To get 25,000 calls a day they must be added to the charity’s SKY Developer team and then claim the upgrade on their subscriptions page. Until someone does both, the integration runs on 1,000 calls a day.
- A partner’s quota only applies in production. The application has to be assigned to the partner’s team and set to production before the higher quota takes effect.
The quota counts calls, not records
Blackbaud is explicit that the limit is on calls, not on the number of records returned. That makes the shape of an endpoint matter more than the size of your database.
- A list endpoint that returns thousands of records in one call is cheap. Listing constituents returns up to 5,000 a page.
- An endpoint you have to call once per record is expensive. Attachments are listed one supporter at a time, so a database of 60,000 supporters costs 60,000 calls: two months on the Free tier, three days on Standard. Our guide to exporting attachments works through that case.
Before estimating any job, write down which calls it makes per record and multiply. It takes ten minutes and prevents most surprises.
How we design within the limits
Retry on 429, everywhere. Every SKY API call goes through one function that, on a 429, waits for the time in Retry-After and tries again a limited number of times. Blackbaud recommends the same pattern. It has to be on every call, including the ones you think will never be busy.
Be careful what you retry. Repeating a read is harmless. Repeating a write can create a second gift if the first attempt did in fact succeed. We retry a write only when the API refused it outright, and we keep a log keyed on the source record so a repeat is recognised.
Do not process a batch in parallel. We learned this on a live integration. One-off online donations arrive minutes apart and never trouble the rate limit. Monthly payments arrive together: our first batch was 15 payments in 11 seconds, each needing several calls, and some were refused. Nothing was lost, because every delivery had been logged before processing, but queueing the batch or retrying politely avoids the problem altogether.
Pace long jobs and make them resumable. A bulk job should run below the rate limit and record what it has finished, so that a quota stop or a server error means carrying on tomorrow, not starting again.
Read once, then cache. Code tables, funds, appeals and campaigns change rarely. Fetch them at the start of a run, not once per gift.
Ask for less. Where an endpoint accepts a list ID, a date filter or a fields parameter, use it. Fewer calls and smaller responses both help.
Which tier do you need?
- A single integration for one charity, such as online gifts into Raiser’s Edge NXT: Standard is ample. A flow of a few hundred gifts a month uses a small fraction of 25,000 calls a day. The task is making sure the upgrade has been claimed.
- A one-off bulk job: Standard, with the job spread over several days, is usually enough. Blackbaud will also consider a temporary increase.
- A product used by many charities: this is what the Partner tier is for. A shared quota across every customer does not scale; a quota per connection does.
If you are hitting the limit today
Check, in this order: whether the Standard upgrade was ever claimed; whether the application is assigned to the right team and set to production; whether a loop is making a call per record that a list endpoint could replace; and whether lookups are being repeated that could be cached. In our experience a quota problem is usually one of these four, and none of them needs a paid upgrade.
We build and run integrations on the SKY API for UK charities. See Raiser’s Edge NXT integration for what we connect, or get in touch if an integration of yours keeps running out of calls.



