Endpoint monitoring use cases
| Endpoint | Monitoring use case |
|---|---|
GET /v2/wallets | Periodically sync your list of wallets (and their latest state). |
GET /v2/wallets/{id} | Refresh a single wallet’s latest status, balances, and positions. |
GET /v2/wallets/{id}/activity | Fetch the activity feed for a wallet. |
GET /v2/wallets/{id}/deposits | List deposits for a wallet. |
GET /v2/wallets/{id}/withdrawals | List withdrawals for a wallet. |
PATCH /v2/wallets/{id}/strategy | Apply a strategy update and track progress via webhooks. |
POST /v2/webhook-endpoints | Subscribe to wallet lifecycle and monitoring events. |
Polling (scheduled monitoring)
For code examples and recommended polling patterns, see Polling.Webhooks (real-time monitoring)
Use webhooks to react to balance changes, deposit status updates, withdrawals (including per-leg payouts), position updates, and strategy status updates.- Example JSON bodies for each event type: Webhook payload examples
- How to verify authenticity of incoming webhook requests: Webhook signature verification
Register a webhook
UsePOST /v2/webhook-endpoints to register your webhook url and the set of event types you want to receive.
For request/response schemas, see the API Reference for POST /v2/webhook-endpoints.