Endpoints
Webhooks
A webhook is a trigger plus a delivery: a saved query or condition paired with where to send it.
| Method | Path | Summary |
|---|---|---|
| POST | https://api.tickerbot.io/ | Canonical create: a webhook is a trigger plus a delivery. |
| GET | https://api.tickerbot.io/ | Fetch one webhook subscription. |
| GET | https://api.tickerbot.io/ | List every webhook subscription on this account. |
| PATCH | https://api.tickerbot.io/ | Edit a webhook subscription in place. |
| DELETE | https://api.tickerbot.io/ | Delete a webhook subscription. |
| POST | https://api.tickerbot.io/ | Re-enable a disabled webhook. |
| POST | https://api.tickerbot.io/ | Send a real-shape test POST to your endpoint, instantly. |
| GET | https://api.tickerbot.io/ | Inspect recent deliveries for a webhook. |
Four doors, one object
POST /v2/webhooks is canonical; four /subscribe shortcuts build the identical webhook.
POST /v2/webhooks is the canonical create — pass a discriminated trigger object (scan, ticker, signal, or event) plus your delivery fields. Four shortcut endpoints build the identical webhook if a simpler body reads better: POST /v2/scan/subscribe, /v2/tickers/{ticker}/subscribe, /v2/signals/{signal}/subscribe, and /v2/events/subscribe. Whichever door you use, the webhook is listed and managed through the registry above — fetch and list, update the trigger or target, audit deliveries, re-enable after auto-suspension, and delete.