Skip to content
TxPipe Docs

Webhook

Sends each event as an HTTP POST to a remote endpoint, with the json-encoded event as the request body. A flexible, dependency-free way to push chain data into any service that can accept an HTTP call.

The sink expects a 200 response for each call: on success it moves to the next event; on failure (at the TCP or HTTP level) it applies the configured retry policy.

Configuration

daemon.toml
[sink]
type = "WebHook"
url = "https://endpoint:5000/events"
authorization = "user:pass"
timeout = 30000


[sink.headers]
extra_header_1 = "abc"
extra_header_2 = "123"
  • type (required): the literal value WebHook.
  • url (required): your endpoint’s URL (must accept POST).
  • authorization (optional): a value to send as the Authorization header.
  • headers (optional): a key-value map of extra headers to send with each call.
  • allow_invalid_certs (optional): skip TLS certificate validation — handy for self-signed certs.
  • timeout (optional, default = 30000): the HTTP response timeout, in milliseconds.