Endpoints
Webhooks
A webhook is the registry record of a subscription — a saved match condition (ticker, signal, or scan) paired with an HTTPS target. On the cadence configured for your plan, we evaluate the condition and POST a webhook.fired event when new tickers enter the match set. See State-change dedup for why one breakout doesn’t fire 500 times. Hobby and above.
Where subscriptions are created
You don’t POST /v2/webhooks — you subscribe on the resource you want to watch. Each subscription creates a webhook record, which then shows up under this registry for management.
POST /v2/tickers/{ticker}/subscribe— Subscribe to a tickerPOST /v2/signals/{signal}/subscribe— Subscribe to a signalPOST /v2/scan/subscribe— Subscribe a scan query
Manage subscriptions via the registry
Every endpoint below operates on the webhook record returned when you subscribed. Use the registry to list, inspect, audit deliveries, re-enable after auto-suspension, and delete.
| Method | Path | Summary |
|---|---|---|
| GET | https://api.tickerbot.io/v2/webhooks | List every webhook subscription on this account. |
| GET | https://api.tickerbot.io/v2/webhooks/{id} | Fetch one webhook subscription. |
| DELETE | https://api.tickerbot.io/v2/webhooks/{id} | Delete a webhook subscription. |
| GET | https://api.tickerbot.io/v2/webhooks/{id}/deliveries | Inspect recent deliveries for a webhook. |
| POST | https://api.tickerbot.io/v2/webhooks/{id}/enable | Re-enable a disabled or pending webhook. |