> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/developer-api/key-concepts/file_scan/webhooks_async_notifications.md).

# Webhooks and Asynchronous Notifications

The Nightfall API supports the ability to send asynchronous notifications when findings are detected as part of a scan request.

The supported destinations for these notifications include external platforms, such as Slack, email, or url to a SIEM log collector as well as to a webhook server.

Nightfall issues notifications under the following scenarios:

* to notify a client about the results of a [file scan request](/developer-api/key-concepts/file_scan.md). File scans themselves are always performed asynchronously because of complexity relating to text extraction and data volume.
* to notify a client about results from a text scan request. Although results are already delivered synchronously in the response object, clients may configure the request to forward results to other platforms such a webhook, SIEM endpoint, or email through a [policy](https://docs.nightfall.ai/docs/using-policies)[.](/developer-api/key-concepts/scanning_features/send_alerts_using_policies.md)

To create a webhook you will need to [access your webhook Signing Key](/developer-api/key-concepts/file_scan/webhooks_async_notifications/webhook_signing_key.md) and then set up a[ create a webhook server.](/developer-api/key-concepts/file_scan/webhooks_async_notifications/webhook_server.md)

For more information on how webhooks and asynchronous notifications are used please see our guides on:

* [Alerting](/developer-api/key-concepts/alerting.md)
* [Using Policies](/developer-api/key-concepts/scanning_features/send_alerts_using_policies.md)
* [File Scanning and Webhooks](/developer-api/key-concepts/file_scan/webhooks.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 by asking a question.

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

```
GET https://help.nightfall.ai/developer-api/key-concepts/file_scan/webhooks_async_notifications.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.