Webhooks

Wallet events 3.0 are posted to one address, in order, signed with your secret. Deliveries are kept for 3 days.

Loading your webhook

Add webhook

https on port 443 only; Shuttle's own addresses are refused.

Event kinds

At least one. All three means no filter.

Start

Webhook address

https on port 443 only, a lower-case host name, no IP address, no credentials or #fragment, up to 1,024 bytes. Shuttle's own addresses are refused. Redirects are not followed.

The position and the secret stay; the next delivery goes to the new address.

Re-issue the signing secret?

New signing secret

This is the only time the secret is shown. Put it in your endpoint's configuration now.

For 24 hours every delivery carries both signatures in Webhook-Signature, v1,new v1,old; verify with either. After that, only the new one. Another re-issue is refused until then.

The new secret did not reach this page

That delivery and everything after it are sent again, in order, with the current address, filter and secret, as new deliveries with new ids. New events wait behind the resend until it catches up.

Your endpoint sees these events a second time; drop repeats by event_id.

Turn off webhooks?

Deliveries stop now. The position and the signing secret are discarded. Turning webhooks on again asks for the address, the kinds and where to start, and issues a new secret.

The event stream and the delivery log are not affected.