> For the complete documentation index, see [llms.txt](https://developer.capsule.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.capsule.video/accessing-videos/webhooks.md).
# Webhooks
### Receive a webhook for each new video
In your account settings, you can specify an endpoint URL that Capsule will POST data to for each new video that is uploaded and processed:
Once set, you will receive a webhook for each new video. This webhook is sent when the video has finished processing — this includes editing, transcoding, and also transcription.
The payload for the webhook is structured like ths:
```
{
"event": "video.processed",
"data": {
"video_id": "mB9QOkKj3eu9",
"capsule_slug": "my-capsule-slug"
}
}
```
Additional event types may be emitted in the future, so you should filter against the value of the "event" key.
After receiving the webhook, you'll generally want to make an API call to fetch the data associated with the object, like this:
```
GET https://api.capsule.video/videos/?slug=
Authorization: Bearer
```
More details on the fetch API can be found [here](/accessing-videos/fetch-api.md).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://developer.capsule.video/accessing-videos/webhooks.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.