View a Hook
View a Hook
Authentication
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.
Path parameters
Response
Max. length: 255 characters
The URL to which the notification is sent.
Returned values: DISABLED, ENABLED
Whether the hook is enabled or not.
Returned values: VALID, INVALID
Whether the hook is valid or not. Once INVALID (following unsuccessful retries) the hook must be disabled and re-enabled.
Returned values: An EventType listed in the event types list
The type of the event.
Max length: 128 characters (see data formats for details)
The unique identifier of the object.
Max. length: 255 characters
Custom data that you can add to this object, such as unique identifiers in your system. To store multiple values, you can serialize them into a single string, for example a JSON object: "{\"id_1\":AB123,\"id_2\":DE456}".
Unix timestamp (UTC) of the date and time the object was created.
Format: A valid email address
The Email address to which alerts are sent in case of consecutive failed notification attempts.
Caution: Mangopay may populate this property automatically if your platform had webhooks integrated in Production before April 2, 2026. If so, setting the Email on a single Hook stops this automatic population for any new Hooks you create - read more.
For all platforms, if this property is returned null then no alerts are sent but the Hook still becomes INVALID after 100 consecutive failed notifications.