Update a webhook
Partial update — include only the fields you want to change.
Common operations:
- Change URL:
{ "url": "https://new-server.com/webhooks" } - Change subscribed events:
{ "events": ["*"] } - Disable (stop receiving events):
{ "isActive": false } - Re-enable:
{ "isActive": true }— this also resets the failure count to 0
Automatic catch-up on re-enable: while an endpoint is disabled (manually or
auto-disabled after consecutive failures), no deliveries are attempted or
recorded for it. When you re-enable it, the events it missed during the
disabled window are automatically re-dispatched to it, oldest first (up to 500
events, looking back at most 7 days), and any deliveries that failed
terminally just before the disable are retried. fill.created is not
included in catch-up — recover missed fills via the event stream’s ?since=
replay or GET /platform/v1/organization/snapshots/fills. Catch-up
deliveries are normal deliveries: same payloads (account state is rendered at
send time), same signatures, and the original event id and createdAt —
dedupe as usual.
Note: To change the signing secret, use the dedicated rotate-secret endpoint instead.
Authentication: Accepts either Authorization: Bearer <jwt> (dashboard) or X-API-Key: hp_live_... (programmatic).
Authorizations
JWT Bearer token for user session auth. Format: "Bearer {token}". Used by User and Organization endpoints.
Path Parameters
Webhook ID
Body
New endpoint URL (HTTPS required)
"https://new-server.com/webhooks"
Updated event subscriptions
1*, account.created, account.status_changed, account.updated, account.imported, account.unlinked, account.passed, account.failed, account.lockout_created, account.lockout_removed, account.lockout_updated, account.payout_processed, account.max_payouts_reached, purchase.created, purchase.status_changed, trader.created, snapshot.ready, fill.created, account.balance_changed Updated label
255"Updated production webhook"
Set to false to pause delivery, true to resume (resets failure count)
false