v2
latestOpenAPI 3.1.02026-07-262279731.3 MBUpdate a Hook
<Warning icon="fa-regular fa-triangle-exclamation"> **Caution – Setting email for consecutive failures after April 2026**In Production, if your platform had VALID Hook objects before April 2, 2026, then Mangopay automatically populates the Email property with the previously used global address unless and until you set it proactively using this endpoint.
If you send the Email on a POST or PUT request, other new Hooks created without the Email do not populate the Email automatically and do not emit alerts in case of consecutive failed notifications or if the Hook becomes INVALID.
Platforms integrating after April 2, 2026 must proactively set the Email to receive alerts.
Read more about this change → </Warning>
Path parameters
Platform's API account identifier, associated with the API key.
The unique identifier of the hook.
Headers
Bearer authentication of the form Bearer <token>, where token is your auth token.
If your platform is using a proxy to take SCA-triggering action on behalf of users, you also need to integrate mTLS authentication and use the api-mtls base URL.
Request body
Response
Success