> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/admin/apis-and-integrations/admin-webhooks.md).

# Webhooks (Admin)

## Overview

The Webhooks section in the Admin Portal lets you view and monitor all webhook subscriptions that have been configured in Designer. Webhooks send real-time HTTP notifications to external systems when specific events occur in Welkin.

For configuring new webhooks, see [Webhooks](https://docs.welkinhealth.com/designer/webhooks/webhooks) in the Designer documentation.

***

## Accessing Webhooks in the Admin Portal

1. Log in to the **Admin Portal**.
2. Navigate to **Integrations → Webhooks**.
3. You will see a list of all configured webhook subscriptions for your environment.

***

## What You Can See

Each webhook entry displays:

* **Name** – the label given to the webhook when it was configured in Designer.
* **URL** – the external endpoint receiving the HTTP POST notifications.
* **Events** – the Welkin events that trigger the webhook (e.g., patient created, assessment completed, CDT record updated).
* **Status** – whether the webhook is currently active or inactive.

***

## Managing Webhooks

From the Admin Portal you can:

* **Enable or disable** a webhook subscription without deleting it.
* **View delivery logs** to see recent webhook events, response codes, and any failures.
* **Retry failed deliveries** if an external endpoint was temporarily unavailable.

To modify the events or endpoint URL of an existing webhook, make the change in **Designer → Webhooks** and publish the configuration.

***

## Related

* [Webhooks (Designer)](https://docs.welkinhealth.com/designer/webhooks/webhooks) – configure webhook subscriptions and event triggers
* [API Clients](/admin/admin.md#api-clients) – manage API credentials used by external integrations


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.welkinhealth.com/admin/apis-and-integrations/admin-webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.