Plexara
Blackbaud Raiser's Edge NXT
- Catalog
- Blackbaud SKY API
- Operations indexed
- 577
- Access
- Read, with a separate read and write connection
The same catalog backs two connections, one limited to reading and one that can also write, so most roles get the first. A knowledge page on the connection records the conventions that fail in misleading ways, with the working recipe beside each one.
Endpoint surface
What the assistant can reach
| Area | Operations | Covers |
|---|---|---|
| Constituent | 164 | Constituents with addresses, phones, emails, relationships, notes, codes, custom fields, and giving summaries. |
| NXT Data Integration | 94 | An expanded set of operations designed for moving data in and out in volume. |
| Event | 65 | Events, participants, fees, and participant donations. |
| Fundraising | 53 | Campaigns, funds, appeals, and packages. |
| Membership | 40 | Memberships, programs, categories, and benefits. |
| Gift | 28 | Gifts with splits, fundraisers, soft credits, and payments. |
| Query | 26 | Define saved queries, run them as jobs, and collect the results. |
| Volunteer | 25 | Volunteers, assignments, and recorded hours. |
| Opportunity | 19 | Major-gift opportunities with fundraisers, attachments, and custom fields. |
| Consent and communication preference | 26 | Consent records, channels, categories, and how each constituent asks to be contacted. |
| Code tables, lists, custom fields, gift batches, standard reports, and webhooks | 37 | Reference tables, saved lists, batch entry, report jobs, and event subscriptions. |
Example questions
Questions an assistant can answer
- What has this donor given over their lifetime, and when was the most recent gift?
- Which annual recurring gifts renew in the next 30 days?
- Who gave to the spring appeal, and through which fund?
- Which memberships lapsed last month, by program?
- Which registered participants for the gala have not yet given this year?
- Which constituents have withdrawn consent for email?
What the agent calls. This is the exchange the agent has with Plexara on your behalf, shown for the technical reader. You ask in plain language; you never type any of it.
| Asked | API | First result |
|---|---|---|
| How much has a donor given over their lifetime? | Blackbaud Raiser's Edge NXT, 577 operations | GET /constituent/v1/constituents/{constituent_id}/givingsummary/lifetimegiving |
Knowledge pages
The knowledge on this connection
The SKY API has conventions that fail in misleading ways. A knowledge page attached to the connection records each one once, with the working recipe beside it.
1
A missing parameter looks like a missing API
Every Query operation needs two fixed product parameters. Leaving them out returns a bare not-found, which reads as a routing or entitlement failure. The page tells the assistant to check the parameters before anything else.
2
A query definition reads in one shape and writes in another
Reading a saved query returns nested field objects. Creating or editing one takes flat field ids. The page records both shapes, so copying a query works.
3
Dates arrive with a time, amounts without a currency sign
With formatting turned off, amounts are bare numbers and dates still carry a midnight time component. The page gives the exact format, so a parser is written once.
4
Gift ids are text
Most gift ids carry a letter prefix. Any table or parser that types them as integers fails on the first row. The page says so.
5
The results link expires in fifteen minutes
A finished query job returns a short-lived download link. Plexara follows the link and saves the file, so the result does not expire unread.
Combinations
Works with
A campaign, from spend to gift. Did the spring membership campaign work, and which channel carried it?
The full index of APIs in production is on the API connections page.
Plexara is not affiliated with or endorsed by Blackbaud. Blackbaud is a trademark of its owner.
Next
API connections
The APIs already in service, and the questions that use more than one of them in a single session.