Skip to main content
There are two integration tracks, depending on how your product connects to Endaoment. Start with Integration Patterns for auth, proxying, idempotency, and amount conventions — it’ll save you some back-and-forth later.

​
Before you begin

Request OAuth credentials from us via Discord support. You’ll start in dev or staging; production credentials come after you’ve validated your integration — see Going to Production.

​
Environments

​
Standard OAuth journey

For apps where donors sign in with OAuth + PKCE and your backend proxies API calls on their behalf. Registered OAuth clients must use POST /v1/funds/partner — not POST /v1/funds. See Open a Fund for routing details.

​
Partner API journey

For tech-platform partners calling our server-to-server APIs with an API key. No donor OAuth login required on your side. Full walkthrough: Partner Journey. API reference: Partner Endpoints.

​
Reference implementation

The GitHub quickstart sample is a working frontend + backend app with OAuth PKCE — handy if you like learning by example, but not required to integrate.