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

# Webhook Alerts

> Signed HTTP notifications when a market, wallet, archive, export, or billing event happens. Set one up with an agent, the dashboard, or the REST API.

Webhook Alerts send a signed HTTP POST to your server, or a message card to a Slack or Discord channel, each time an event you chose happens: a large liquidation, a funding flip, a fill by a wallet you follow, a finished export. Set one up with an agent, the dashboard, or the REST API.

<Card title="Send your first test delivery" icon="rocket" href="/webhooks/quickstart" horizontal>
  Run a small receiver, register it, check a signed test delivery, then create a live alert for Hyperliquid BTC liquidations of \$250,000 or more.
</Card>

## Three ways to set one up

All three create the same endpoints and rules through the same API, so you can start in one and continue in another: a rule an agent creates shows up in the dashboard, and a rule built in the dashboard can be read and edited over REST.

<CardGroup cols={3}>
  <Card title="Talk to an agent" icon="bot" href="/webhooks/quickstart">
    Connect an MCP client to the hosted 0xArchive server and describe the alert you want. The agent sizes the rule against history, creates it, and checks that a test delivery arrived.
  </Card>

  <Card title="Use the dashboard" icon="layout-dashboard" href="https://0xarchive.io/dashboard?tab=webhooks&utm_source=docs&utm_medium=referral&utm_campaign=docs_referral&utm_content=webhooks_dashboard">
    Open Webhooks in the dashboard. Add an endpoint, build a rule, see how often it would have fired before you save it, and read the delivery log.
  </Card>

  <Card title="Call the REST API" icon="square-terminal" href="/webhooks/quickstart#with-the-rest-api">
    Create endpoints and rules from your own code or the SDKs with your API key. The quickstart has the calls, and the API overview lists every route.
  </Card>
</CardGroup>

## Alerts in a chat channel

To get alerts in Slack or Discord without running a receiver, register the channel's incoming-webhook URL as the endpoint, in the dashboard or with the same create call: a Slack URL starting `https://hooks.slack.com/services/`, or a Discord URL starting `https://discord.com/api/webhooks/`. The endpoint's `format` is detected from the URL as `slack` or `discord`, and each alert arrives as a message card instead of the signed JSON that the receiver in the quickstart checks. A test delivery posts a short card saying the channel is connected. Rules, the estimate, the delivery log and the plan allowances work the same way for every endpoint.

## How it works

* **An endpoint** is the URL that receives deliveries. Each one has its own signing secret, shown once when you create it.
* **A rule** points one endpoint at one event type, optionally narrowed by venue, symbols, watched addresses, conditions and parameters. The API and the dashboard call a rule a *subscription*: its routes are under `/v1/webhooks/subscriptions`, and the dashboard button is **New subscription**. A rule with no configuration matches every event of its type.
* **A delivery** is one POST to your endpoint. It is retried until your receiver answers with a 2xx or 24 hours pass, and each delivery has an entry in the endpoint's delivery log.
* **Watched addresses** are the wallets your `account.*` rules report on. The dashboard lists them under **Watched wallets**.

Events cover liquidations, funding flips, open interest moves, market breadth, HIP-3 oracle jumps, HIP-4 settlements, new listings and Hyperliquid node upgrades, the activity of watched addresses, the health of the archive itself, finished exports and your own credit balance.

## Plan availability

Webhook delivery starts on the Build plan. The estimate and the dry-run answer on every plan, Free included, for the event types each one supports; [Estimate and dry-run](/webhooks/estimate-and-dry-run#which-event-types-can-be-previewed) lists them. A wallet event type also needs a watched address to preview, and Free cannot hold one. Endpoints, rules, watched addresses and deliveries a day grow with each plan, and deliveries do not use API credits; [Limits and plans](/webhooks/limits-and-plans) has the numbers.

## Go further

<CardGroup cols={2}>
  <Card title="Events" icon="list" href="/webhooks/events">
    Every event type by category: what it reports, which venues it covers, and how fast it arrives.
  </Card>

  <Card title="Rules" icon="sliders-horizontal" href="/webhooks/rules">
    Scope a rule by venue, symbol and address, add conditions and relative thresholds, and set the parameters that define an occurrence.
  </Card>

  <Card title="Estimate and dry-run" icon="chart-column" href="/webhooks/estimate-and-dry-run">
    See how often a rule would have fired, and which events it would have delivered, before you create it.
  </Card>

  <Card title="Watched addresses" icon="wallet" href="/webhooks/watched-addresses">
    Register the wallets whose fills, liquidations, transfers and orders you want to hear about.
  </Card>

  <Card title="Signatures and payloads" icon="shield-check" href="/webhooks/signatures-and-payloads">
    Check the signature on every delivery, read the event envelope, and build a receiver that does not lose events.
  </Card>

  <Card title="Delivery and retries" icon="refresh-cw" href="/webhooks/delivery-and-retries">
    Find out why deliveries stopped, then retries, the delivery log, redelivery, secret rotation and paused rules.
  </Card>

  <Card title="Limits and plans" icon="gauge" href="/webhooks/limits-and-plans">
    What each plan allows, how deliveries are counted, and what Free can do before you upgrade.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.