Skip to main content
withdrawal.requested Sent when a wallet starts the withdrawal timelock. Use it to show pending withdrawal state and the earliest expected finalization time.

​
Event fields

​
id
string
required
​
type
string
required
withdrawal.requested
​
created_at
string
required
ISO 8601 datetime
​
api_version
string
required
​
data
object
required
​
data.withdrawal_id
string
required
​
data.user_address
string
required
​
data.asset_address
string
required
​
data.amount
string
required
​
data.network
string
required
​
data.requested_at
string
required
ISO 8601 datetime
​
data.available_at
string
required
ISO 8601 datetime
Earliest configured finalization time. Open obligations may still delay exit.
​
data.transaction_hash
string
required
​
data.status
string
required
pending

​
Event examples

Payload
{
  "id": "evt_01JY3N7A4Q8H2C5M6R9V0X1BKT",
  "type": "withdrawal.requested",
  "created_at": "2026-06-22T16:00:00.000Z",
  "api_version": "2026-06-01",
  "data": {
    "withdrawal_id": "wd_01JY3N6Z",
    "user_address": "0x1111111111111111111111111111111111111111",
    "asset_address": "0x3333333333333333333333333333333333333333",
    "amount": "5000000",
    "network": "eip155:84532",
    "requested_at": "2026-06-22T15:59:55.000Z",
    "available_at": "2026-07-14T15:59:55.000Z",
    "transaction_hash": "0xWithdrawalRequestTransaction",
    "status": "pending"
  }
}
  • Display the withdrawal as pending, not completed.
  • Treat available_at as the earliest configured finalization time.
  • Check open guarantees and settlement obligations before telling a user that funds are withdrawable.
  • Reconcile current state if this event arrives after a finalization event.
See deposits and withdrawals.