Changelog · Last updated May 16, 2026

Product updates

Highlights from recent releases. For integration behaviour and limits, the guides in the left nav stay the source of truth — this page is the digest.

Webhook delivery log + signed payloads

Every outbound webhook is now easier to trust and debug end-to-end: you get a delivery timeline on each submission, and requests carry stable SaveForm identifiers alongside optional auth headers you configure.

Delivery log

Each POST is recorded with HTTP status, timing, a response excerpt, and the reason when nothing was sent (spam skip, quota, inactive webhook). Failures stay visible — there are no silent retries — and you can fire a manual retry from the submission row when you have fixed the downstream endpoint.

Verifier-friendly outbound requests

Alongside the JSON or form body, SaveForm sends User-Agent: SaveFormIO-Webhook/1.0 and X-SaveForm-Webhook-Id on every call so your receiver can reject traffic that does not look like ours. Layer Bearer tokens, API keys, Basic auth, or custom headers on top so only your stack can accept authenticated payloads over HTTPS.

Learn more

Delivery & retries — logging, failures, manual retries, and the test button.
Authentication — auth modes and identifying SaveForm traffic.
Submissions dashboard — row-level webhook status and debugging workflow.