Skip to main content
The URL of a trigger, as trigger.url returns it. Any service posts JSON events to it. It takes no API key: the URL is unguessable, and a trigger with verification requires an HMAC-SHA256 signature of the body with the trigger’s secret.

Answers

paddock answers in this order and records a delivery for every request to an existing trigger. A 2xx answer means the delivery is stored; the rules’ work happens after it. A rejected request’s error body names the delivery recorded for it in details.deliveryId, so you can find it in the trigger’s deliveries.
202 Accepted
200 OK (duplicate)
401 Unauthorized
The answer never says what the rules or the agents will do: those are the delivery’s outcomes, which you read with trigger.deliveries.get(deliveryId) or in the console.

Try it

For a trigger that verifies signatures, sign the exact bytes you send: