SpringAPIs let your institution read and write AwardSpring data from your own systems, so student, donor and giving information can flow between AwardSpring and your SIS, CRM or data warehouse without anyone rekeying it.
Common uses include pulling award and scholarship data, syncing donor and gift records, and triggering your own workflows when something happens in AwardSpring.
Full documentation
Complete SpringAPIs and webhooks documentation lives on the AwardSpring developer site, covering authentication, conventions, webhooks and the full API reference. It is kept current as endpoints change.
That site is the source of truth for everything technical. It is written for whoever is building the integration, and it is kept current as endpoints change.
It covers:
Section | What is there |
Getting Started | Introduction, and the official .NET and PHP SDKs |
Conventions | Authentication, pagination, errors, idempotency, rate limits and dry runs |
Webhooks | Overview, signature verification, delivery and retries, and the event types you can subscribe to |
API Reference | Endpoints for award cycles, donors, donor activities, funds, gifts and scholarships |
Webhooks
Alongside the API, SpringAPIs supports webhooks. Instead of your system repeatedly asking AwardSpring whether anything has changed, AwardSpring notifies your system when something happens, for example a gift being recorded or a student completing an application.
Webhooks are documented in full at docs.awardspring.com, including signature verification, delivery and retry behavior, and the available event types.
A few things to know before you start
Every request needs an API key. Requests authenticate with your institution's secret key in the X-Spring-API-Key header. The key is scoped to your institution, so it only ever returns your own data. Treat it like a password: store it somewhere secure, never put it in client side code or a public repository, and contact support if you think it has been exposed.
Data uses snake_case. Field names are lowercase with underscores.
Lists are paginated. List endpoints return results in a list envelope with a cursor. Pass the next_cursor value back as starting_after to get the following page, rather than expecting everything in one response.
Errors come back as JSON. Every error includes a machine readable code, so your integration can handle failures rather than only logging them.
Availability
SpringAPIs are available to:
Donor management customers
Scholarship management customers on the Enterprise tier, or who have purchased integrations as an add-on to their subscription
If you are not sure whether your subscription includes API access, please reach out.
Generating a Token
Once enabled, the API & Integrations tab will appear in your Settings, allowing your team to:
Generate secure access tokens
Monitor API activity
Revoke or regenerate tokens at any time
Share tokens with your IT or integration team
This workflow mirrors what developers expect from modern SaaS platforms, ensuring a smooth technical onboarding experience.
Note: You are able to create up to 10 tokens at one time.
