CHANNEL — WEBHOOKS

Price crosses, as JSON.

For bots, dashboards, spreadsheets and anything else you run: coinsentry POSTs a JSON payload to your endpoint the moment a price crosses your level — pair, exchange, target price, current price, timestamp. New-listing and delisting events POST the same way. Set a signing secret and every delivery arrives HMAC-signed so you can verify it's really us — with custom headers and method if your receiver is picky. It's the alert infrastructure you'd build, minus the exchange-polling half.

WEBHOOK — SPEC
CHANNELWEBHOOK
SETUP TIMEMINUTES
MEDIAN DELIVERY2.8S
PLANSUNLIMITED
ALERT CAPNONE ON UNLIMITED
START GETTING PINGED

30-DAY FREE TRIAL — NO CARD

01SETUP

Webhook alerts in three steps

  1. 01
    Add your endpoint

    Dashboard → Channels → Webhook. Paste your URL, pick method and headers if needed, and set an optional signing secret.

  2. 02
    Verify the signature

    With a secret set, each delivery is signed — HMAC-SHA256 of the raw body — one middleware line to confirm authenticity.

  3. 03
    Act on the payload

    JSON in, action out: log it, trade on it, forward it. If your endpoint is down we retry automatically.

START GETTING PINGED30-DAY FREE TRIAL — NO CARD
02THE ALTERNATIVE

Versus polling exchange APIs

Rolling your own means juggling 13 exchanges' REST quirks, WebSocket reconnects, and rate limits — before you write a line of strategy. A coinsentry webhook inverts it: we watch the feeds, you receive one clean POST when your condition is true. Push, not poll.

QUICK START: EXACT PAYLOAD + HMAC VERIFICATION →
03FAQ

Fair questions, straight answers

Q1What does the webhook payload contain?

JSON with the pair, exchange, your target price, the price that triggered, and the timestamp of the cross.

Q2Can I get new-listing alerts as webhooks?

Yes. Listing alerts fire in up to two phases — Announced, when an exchange publishes a listing notice ahead of the open, and Live, the moment the pair starts trading. The announced phase exists for the exchanges that publish a notice feed we watch (Binance, Bybit, OKX, Bitget and KuCoin); every other tracked exchange is caught live, off its own market data. Following an exchange covers delistings too, on every plan. Webhook delivery is part of the Unlimited plan — listings on all 13 exchanges, to the same endpoints as your price alerts.

Q3What does a listing webhook payload contain?

JSON with an event field — "listing_announced", "listing_live" or "delisting" — plus the exchange name, the base asset symbol, the pair symbols, the trading start and detection timestamps (milliseconds), and the source URL of the exchange's notice. Deliveries carry the same HMAC X-Coinsentry-Signature header as price alerts.

Q4How do I know a webhook call is genuine?

Set a per-endpoint secret and every delivery is signed — HMAC-SHA256 of the raw request body, sent in the signature header.

Q5What if my endpoint is down?

Failed deliveries retry automatically. Our delivery pipeline's uptime is public and independently monitored.

Q6Can I set custom headers or method?

Yes — custom headers and HTTP method per endpoint, so it slots into existing auth schemes.

Q7How fast do webhooks fire?

Median delivery is 2.8 seconds from the price crossing to the ping arriving.

Know
first.

Ten seconds to set an alert.

LAUNCH COINSENTRY30-DAY FREE TRIAL — NO CARD