Browse documentation
Build
Destinations
Destinations are where verified events go. Add several to one endpoint when different systems need the same event — each gets its own retry schedule and delivery history.
HTTPS endpointJSON or form body, custom headers
SlackPost formatted messages to a channel
GitHubDispatch repository events
EmailSend a readable event summary
Add a destination
POST /v1/endpoints/ep_7a3k2/destinations
curl -X POST "https://api.hooks.events/v1/endpoints/ep_7a3k2/destinations" \
-H "Authorization: Bearer $HOOKS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://api.acme.com/hooks/orders",
"method": "POST",
"auth": { "type": "bearer", "token": "$DOWNSTREAM_TOKEN" }
}'Inbound secrets and cookies are never forwarded. Configure a separate outbound credential for each destination.
Was this page helpful?
Tell us if something was missing or unclear.
Ready to try it?Create a free workspace and send your first event.