Endpoint
POST /v3/webhooks/update
Authentication and target
Access is resolved through the authenticated credential owner. Account credentials can target only their own account. User credentials must supplyaccount_number for transaction events and omit it for VA Account KYB. Platform credentials can manage only Master Account KYB and must omit account_number. See Webhook Management for the complete event/owner matrix.
Do not send X-ISPB or X-Account-Number with a platform or user credential. An account credential may omit both headers; if sent, both are required and must match its bound account.
Request body
Success data
The updatedwebhook object with webhook_id, event_type, callback_url, status, created_at, and updated_at.
Behavior and validation
If both callback URL and status are supplied, the URL update is applied before enable/disable. The API has no version precondition and does not reject an otherwise empty patch at the v3 handler layer.Errors
Every call can fail for missing or invalid signature headers, an expired timestamp, nonce replay, an invalid body hash or signature, insufficient permission, or a downstream service error. Endpoint-specific errors include:field_invalidfor an unsupported status or a supplied blank callback.permission_deniedfor an unsupported owner/event/account combination.not_foundwhen the subscription is not visible.