Check a direct deposit transaction

Error

A valid request URL is required to generate request examples

{
  "status": "not-detected"
}

{
  "defined": true,
  "code": "BAD_REQUEST",
  "status": 400,
  "message": "Invalid request",
  "data": {
    "error": "<string>"
  }
}

{
  "defined": true,
  "code": "NOT_FOUND",
  "status": 404,
  "message": "This campaign isn't accepting direct deposits",
  "data": {
    "error": "<string>"
  }
}

GET

campaigns

{campaignId}

donation-echo

status

Error

A valid request URL is required to generate request examples

{
  "status": "not-detected"
}

{
  "defined": true,
  "code": "BAD_REQUEST",
  "status": 400,
  "message": "Invalid request",
  "data": {
    "error": "<string>"
  }
}

{
  "defined": true,
  "code": "NOT_FOUND",
  "status": 404,
  "message": "This campaign isn't accepting direct deposits",
  "data": {
    "error": "<string>"
  }
}

Authorizations

donate-api-key

string

header

required

Developer API key. Required for config create/list and project analytics. The disabled config DELETE endpoint also requires authentication. Optional on public GET reads (anonymous callers are IP rate-limited). Obtain from the Developer dashboard.

Path Parameters

campaignId

string

required

Campaign id

Query Parameters

chainId

number

required

Chain id the donor sent on

transactionHash

string

required

Source transaction hash (EVM) or signature (Solana)

Response

status

enum<string>

required

Available options:

not-detected,

detected,

forwarding,

delivering,

received,

needs-review,

reorged