Skip to main content
WEBHOOK

Event Types

  • POOL_DEPOSIT_REQUEST.REJECTED - A submitted pool account deposit was rejected during review

Sample Payload

Pool Deposit Rejected

rejectionReason is free text entered by the reviewer. Show it to your operator; do not branch on its contents. Branch on resubmissionRequired instead: true means you can correct the submission and send fresh proof, false means the rejection is final.
To test this event, submit proof in sandbox and have it rejected. Trigger Test Webhook can’t send it.
This payload is a flat, purpose-built shape rather than the full transaction object used by Transaction Events. If you need the full transaction, fetch it with Get Transaction using transactionId.

Body

application/json
id
string<uuid>
required

Unique ID of this event. Every delivery attempt of the same event carries the same id, so use it to ignore a delivery you have already processed.

Example:

"8f14e45f-ceea-4e7a-9f1d-6b1c2a3d4e5f"

event
enum<string>
required

Identifies which pool deposit event occurred

Available options:
POOL_DEPOSIT_REQUEST.REJECTED
Example:

"POOL_DEPOSIT_REQUEST.REJECTED"

createdAt
string<date-time>
required

When Afriex created the event. Retries keep this value, and the signature covers it, so you can reject a delivery that is older than you expect.

Example:

"2026-04-24T09:13:33.883Z"

data
object
required

Details of the rejected pool deposit. A flat, purpose-built shape rather than the full transaction object. Fetch the transaction with GET /api/v1/transaction/{transactionId} if you need the rest of it.

Response

Acknowledge receipt. Return any 2xx status code quickly. Response body is ignored.