---
title: "View a Hook"
method: GET
path: "/v2.01/{ClientId}/hooks/{HookId}"
tags: ["Webhooks"]
---

# View a Hook

`GET /v2.01/{ClientId}/hooks/{HookId}`

## Request

- Base URL: `https://api.sandbox.mangopay.com`
- URL: `https://api.sandbox.mangopay.com/v2.01/{ClientId}/hooks/{HookId}`
- Auth: HTTP bearer

View a Hook

## Path parameters

- `ClientId` string, required
- `HookId` string, required

## Response `200`

Success

- HookResponse
  - `Url` string: Max. length: 255 characters The URL to which the notification is sent.
  - `Status` string: **Returned values:** `DISABLED`, `ENABLED` Whether the hook is enabled or not.
  - `Validity` string: **Returned values:** `VALID`, `INVALID` Whether the hook is valid or not. Once `INVALID` (following unsuccessful retries) the hook must be disabled and re-enabled.
  - `EventType` string: **Returned values:** An `EventType` listed in the <a href="/webhooks/event-types">event types list</a> The type of the event.
  - `Id` string: Max length: 128 characters (see [data formats](/api-reference/overview/data-formats) for details) The unique identifier of the object.
  - `Tag` string: 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}"`.
  - `CreationDate` integer: Unix timestamp (UTC) of the date and time the object was created.
  - `Email` string: Format: A valid email address The `Email` address to which alerts are sent in case of [consecutive failed notification attempts](/webhooks#notification-retries-and-failure). **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](/webhooks#transition-from-default-email-april-2026). 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.

## Changes

- **2026-09-17** `f44a59c76515`: 1 warning, 1 info
  - deleted the `header` request parameter `Authorization`
  - the endpoint scheme security `oauth2` was added to the API
- **2026-09-12** `8e731ec4a85b`: 1 info
  - api operation id `view_hook` removed and replaced with `webhooks_view_hook`

[Operation history](https://skmtc.dev/mangopay/apis/mangopay/changes/v2.01/:ClientId/hooks/:HookId/get.md)

---

[API](https://skmtc.dev/mangopay/apis/mangopay.md) - [All operations](https://skmtc.dev/mangopay/apis/mangopay/llms.txt) - [OpenAPI document](https://skmtc.dev/mangopay/apis/mangopay/revisions/380b21eb80ae?raw)
