This is Peeve sending to you. It is not the inbound connector plumbing for
WhatsApp or Slack, which Peeve configures on your behalf and which is not a
customer surface.
Setup
Two equivalent paths — Connectors → Webhooks in the dashboard, or the API. An endpoint created through the API is the same row with the same guarantees, and it flips the Connectors card to connected just the same. Peeve issues a signing secret (whsec_…) when you create the endpoint.
Use the test-send to confirm your receiver works before you rely on it. A test
delivery carries livemode: false and a Peeve-Test: true header, and is capped
at 20 per endpoint per hour.
Verifying a request — read this first
The signed string is"<timestamp>.<raw body>". The timestamp is inside the
HMAC, so a captured request cannot be replayed with a rewritten header.
Three rules:
- Sign the raw body bytes, exactly as received. Re-serialising parsed JSON produces different bytes and the check will fail.
- Compare in constant time.
- Reject anything older than about five minutes.
The envelope
Headers
Event catalogue
Status vocabularies
Retries and idempotency
Delivery log
Connectors → Webhooks → your endpoint → Recent deliveries. Each row records the event, the channel, the outcome, your HTTP response code, the attempts taken and how long it took.Managing endpoints
There is no third lifecycle state; this matches the connector UI’s two
operations exactly.Reach for rotate-secret, not delete-and-recreate, when a secret leaks —
recreating changes the endpoint id and throws away its delivery history.
Destination requirements
Enforced on update as well as create, so an endpoint cannot be edited into a private address:- HTTPS only —
http://is a400. - No
localhost, no RFC-1918 private ranges, no IPv6 loopback, no link-local169.254.169.254, no.internal, no non-HTTP schemes.
blocked in the delivery
log.