Fund a DAF - Endaoment

Outcome

A wire donation pledge is created for the selected fund. The user receives wire instructions and a pledge ID to track the inbound transfer.

When

After Open a Fund. Trigger when the user chooses to contribute by bank wire. This guide covers the wire flow end to end. Other donation types are listed below with API links only.

Auth

Call	Auth
`GET /v1/funds/mine`	Bearer
`GET /v1/donation-pledges/wire/details/domestic`	Public
`POST /v1/donation-pledges/wire`	Bearer

Endpoints (wire flow)

Step	Method	Path	API reference
1. List user’s funds	GET	`/v1/funds/mine`	List my funds
2. Get wire instructions	GET	`/v1/donation-pledges/wire/details/domestic`	Get domestic wire details
3. Create wire pledge	POST	`/v1/donation-pledges/wire`	Create wire donation pledge

International wire instructions: Get international wire details. See also: Donations in API reference.

Required inputs (wire pledge)

Field	Description
`receivingFundId`	Target fund from `/v1/funds/mine`
`pledgedAmountMicroDollars`	Donation amount in microdollars
`idempotencyKey`	New UUID per submission
`donorIdentity`	Optional override of donor identity — omit to use the authenticated user’s stored identity. If provided, must include `firstName`, `lastName`, `email`, and `address`

See the API reference for the full request schema.

Example: create wire pledge

Omit donorIdentity to use the authenticated user’s identity (typical quickstart path):

curl -X POST "https://api.dev.endaoment.org/v1/donation-pledges/wire" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "receivingFundId": "FUND_UUID",
    "pledgedAmountMicroDollars": "100000000",
    "idempotencyKey": "550e8400-e29b-41d4-a716-446655440000"
  }'

To override donor identity, include a complete donorIdentity object with address:

curl -X POST "https://api.dev.endaoment.org/v1/donation-pledges/wire" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "receivingFundId": "FUND_UUID",
    "pledgedAmountMicroDollars": "100000000",
    "idempotencyKey": "550e8400-e29b-41d4-a716-446655440000",
    "donorIdentity": {
      "firstName": "Alex",
      "lastName": "Donor",
      "email": "alex@example.com",
      "address": {
        "line1": "123 Main St",
        "city": "San Francisco",
        "state": "CA",
        "zip": "94105"
      }
    }
  }'

Response you need

Field	Use
Pledge `id`	Track donation status
Wire details (step 2)	Show user where to send funds

Other donation types

Type	Endpoint	API reference
Crypto	`POST /v1/donation-pledges/crypto`	Create crypto donation pledge
Stock	`POST /v2/donation-pledges/stock`	Create stock donation pledge
DAF migration	`POST /v1/donation-pledges/daf-migration`	Create DAF migration pledge

Common mistakes

Using fundId / amount field names (API expects receivingFundId / pledgedAmountMicroDollars)
Providing partial donorIdentity without address (omit the object entirely or include all required fields)
Using dollar amounts instead of microdollars
Reusing idempotencyKey for different pledge attempts

Next: Find a Nonprofit

​Outcome

​When

​Auth

​Endpoints (wire flow)

​Required inputs (wire pledge)

​Example: create wire pledge

​Response you need

​Other donation types

​Common mistakes