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

EnvironmentAuth URLAPI URL
Devhttps://auth.dev.endaoment.orghttps://api.dev.endaoment.org
Staginghttps://auth.staging.endaoment.orghttps://api.staging.endaoment.org
Productionhttps://auth.endaoment.orghttps://api.endaoment.org

​
Standard OAuth journey

For apps where donors sign in with OAuth + PKCE and your backend proxies API calls on their behalf.
StepOutcomeKey endpointGuide
1User has an access token/auth → /tokenAuthenticate
2Donor has a fundPOST /v1/funds/partnerOpen a Fund
3Donation pledge createdPOST /v1/donation-pledges/wireFund a DAF
4Nonprofit selectedGET /v2/orgs/searchFind a Nonprofit
5Grant submittedPOST /v1/transfers/async-grantsRecommend a Grant
6Production-ready—Going to Production
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.
StepOutcomeKey endpoint
1Partner user provisionedPOST /v1/auth/partner/users
2Partner fund createdPOST /v1/funds/partner
3Settled donation recordedPOST /v1/donation-pledges/partner/*-settled
4Grant submittedPOST /v1/transfers/partner/grant-submissions
5Missing org reportedPOST /v1/missing-org-reports/tech-platform
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.