Record a gift and list existing gifts for a constituent via the Blackbaud SKY API (Gift API)
domain: developer.blackbaud.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with OAuth2 and obtain the Bb-Api-Subscription-Key as with any SKY API call
Look up the constituent ID for the donor first (Constituent API) since gifts must be linked to an existing constituent
POST a new gift object to the Gift API (gift endpoints under api.sky.blackbaud.com), specifying constituent ID, amount, gift type, date, and fund/campaign/appeal designations
For pledges, use the pledge-payment sub-resource to record payments against an existing pledge rather than creating a standalone gift
GET the gifts list endpoint filtered by constituent ID to retrieve gift history
Confirm which gift API version (v1 vs. the newer v2 'gft-gifts' surface) your environment exposes before building field mappings, since field names differ between versions
Known gotchas
Blackbaud has been migrating gift endpoints between a legacy Gift API (v1) and a newer Gift API v2 — check current subscription docs for which fields/paths apply to your tenant
Fund, campaign, and appeal IDs must already exist in the RE NXT database (created via the UI or their own SKY API endpoints) before they can be referenced on a gift
Gift webhooks exist separately from the REST API — don't assume creating a gift via API automatically fires the same downstream events as a UI-entered gift in every configuration
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?