> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhook Delivery and Event Types

> Understand signed SEC API webhook deliveries, inspect delivery history, and configure organization endpoints safely.

SEC API sends signed delivery events to organization webhook endpoints. Use an endpoint for monitor matches, delivery notifications, or another event listed by the public event catalog.

## Configure endpoints safely

Create endpoints, rotate secrets, send test deliveries, replay failures, and change subscriptions in the signed-in [SEC API dashboard](https://secapi.ai/app/webhooks). These are human-authenticated organization actions. API keys deliberately cannot mutate them.

Save the signing secret when the dashboard shows it. Verify every incoming request against the exact raw body and `x-secapi-signature` before parsing JSON. Never log the secret or the unverified payload as trusted data.

## Inspect delivery history

Open the signed-in [SEC API dashboard](https://secapi.ai/app/webhooks) to inspect delivery history and the current public event catalog. Use the response status, attempt count, timestamps, event type, and request ID to debug a destination.

Webhook endpoint inspection belongs to the same human-authenticated organization boundary as endpoint configuration. Preserve the identifiers you need for an investigation, then return to the dashboard rather than attempting a control-plane call with an API key.

## Monitor events

`monitor.match` is the event emitted when a saved filing monitor finds new matches. Monitor dispatch is scheduled, so a webhook is a prompt to inspect source-backed filing data, not a claim of instant EDGAR delivery.

## Read next

* [Monitor SEC filing events](/monitors)
* [Build a filing monitor](/tutorials/build-filing-monitor)