Outgoing webhooks
not builtThis page is the design; Jadpo doesn't do this yet. See What is built.
Outgoing webhooks let your app's customers receive its events at an
address of their own. They are built on publishing
(Where events travel): a
customer registers an address, and the public events you choose are
delivered to it, typed from the event, signed and retried.
The customers' addresses can't be listed as connections, so outgoing webhooks get one network exception, owned by the runtime. Its guards are fixed:
- HTTPS only;
- no private, loopback or link-local addresses, checked on the resolved address at every attempt;
- no redirects followed.
The exception is listed once in the network report (The network report). Nothing else in your app, a package included, can reach an address that isn't a declared connection.
Outgoing webhooks aren't built yet (What is built), and nothing stands in for them: your app reaches only the connections it declares, so it can't send to an address a customer gives it. Receiving a webhook is built (Receive a webhook).
Markdown for agents: /docs/outgoing-webhooks.md.Built from Jadpo main at aee2e8f.