Webhooks and events
Receive trades and account changes on your server, check delivery health and fix a webhook that was switched off.
What events are
Events tell you what happened on your accounts: order and position changes, new deals, connection changes, rejected passwords, risk breaches and plan reminders. API → Events shows the latest 200 with a filter by type.
Webhooks
A webhook sends events to an HTTPS URL on your server, signed with a secret so you can verify they come from us. Webhooks are created and changed through the API (
POST /v1/webhooks); the secret is shown once when you create or rotate it. You can have up to 10.Your endpoint should answer with a 2xx status quickly and process the events afterwards.
Check delivery health
API → Webhooks shows each webhook as Healthy, Failing, Off or Disabled after failures, with the last delivery and the next retry. Show deliveries lists recent attempts with the HTTP status and duration.
Failed deliveries are retried with growing pauses (up to one hour apart). A webhook that keeps failing for 72 hours is switched off.
Fix a failing webhook
- Check that the URL is reachable from the internet over HTTPS with a valid certificate.
- Make sure your endpoint answers within a few seconds and doesn't reject our requests (firewall, authentication).
- Send a test delivery with
POST /v1/webhooks/{id}/testand look at the result. - Turn a disabled webhook back on with
PATCH /v1/webhooks/{id}and{ "enabled": true }, then catch up on missed events with the event feed (GET /v1/events?after=…), which keeps 14 days.
For developers
The API side of this topic, with every field and code examples: