> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/admin-panel/webhooks-callbacks/callbacks-admin-ui/manage-callbacks.md).

# Manage Callbacks

View and manage mailbox callbacks in the admin panel, including how to select a mailbox and interpret callback list columns.

An envelope callback is a feature that allows you to receive a notification at the specified URL when an envelope appears in the mailbox according to the configured filters. You can set up callbacks for mailboxes to receive envelope notifications outside the platform. This is done via API.

### Open callbacks

<figure><img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FkpRgsZKFpczJxrjxSH0t%2Fimage.png?alt=media&amp;token=75b240b1-1b9e-437d-b911-df0362981960" alt=""><figcaption></figcaption></figure>

1. Navigate to the **Callback** tab in the admin panel.
2. In the drop-down list, select the mailbox whose callbacks you want to display.

A list of callbacks is displayed for the selected mailbox if callbacks have been configured via the API. Otherwise, the page is displayed as an empty folder.

### Callback list columns

<figure><img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FP59W43xBcCf6F030LOe6%2Fimage.png?alt=media&amp;token=efc3c419-3793-4c75-86a1-d38c51d74fcb" alt=""><figcaption></figcaption></figure>

The list of callbacks contains the following information:

1. Callback URL.
2. Authentication type:\
   — basic\
   — none
3. Success code.
4. Filter — list of specified filters for a specific callback.
5. Action buttons:\
   — settings\
   — delete


---

# 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://support.docstudio.com/admin-panel/webhooks-callbacks/callbacks-admin-ui/manage-callbacks.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.
