Update transaction hash for a crypto donation pledge

curl --request PATCH \
  --url https://api.endaoment.org/v1/donation-pledges/{id}/transaction-hash \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "transactionHash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
}
'

Donation Pledges

Update transaction hash for a crypto donation pledge

Updates the transaction hash for an existing crypto donation pledge.

Authorization rules:

When a pledge was created by an authenticated user, only the user who created the pledge can update it
When the pledge was created by an anonymous user, anyone can update the hash of the pledge. But that update can only occur once.
For pledges created by authenticated users, the hash can be updated multiple times
Transaction hash must be unique across all active pledges for the same token

PATCH

donation-pledges

{id}

transaction-hash

Update transaction hash for a crypto donation pledge

curl --request PATCH \
  --url https://api.endaoment.org/v1/donation-pledges/{id}/transaction-hash \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "transactionHash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
}
'

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

Body

application/json

transactionHash

string

required

Transaction hash proving that the asset was sent to the entity

Example:

"0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"

Response

Transaction hash successfully updated

Complete a donation pledge Upload a missing-org determination letter PDF

⌘I

Documentation Index

Authorizations

Path Parameters

Body

Response