Format webhook 3xx: Sume does not follow redirects, use the final URL

A webhook endpoint that redirects counts as a failed delivery attempt. Register the final HTTPS URL, mind www and trailing-slash redirects, then redeliver.

5 min readSume
All posts

If your webhook endpoint answers with a redirect, Sume counts the delivery as failed. The delivery docs say redirects are not followed, so a 301, 302 or 308 is not a success and the attempt is retried on the schedule. The usual causes are an HTTP to HTTPS bounce, a www to apex rule, or a trailing slash added by your framework.

The fix is to register the exact URL that answers 2xx on its own, and to check it with a plain request before you create a run.

How do I find the redirect?

Request the URL you registered without following redirects and read the status.

curl -sS -o /dev/null -w '%{http_code} %{redirect_url}\n' \
  -X POST https://example.com/hooks/sume \
  -H 'content-type: application/json' \
  -d '{}'

What does the delivery require?

Sume's Run webhooks page sets the rules; the redirect rule is easy to miss next to them.

Webhook delivery rules for Format runs, from Sume's docs, read 2026-10-04.
RuleValue
SuccessA 2xx response within 10 seconds
RedirectsNot followed; a 3xx is a failed attempt
AttemptsUp to 10, with exponential backoff
URLPublic HTTPS, checked again at delivery time

What if the run already ended?

Fix the URL, then ask Sume to send the event again with POST /v1/format-runs/{id}/webhook/redeliver. Meanwhile the run's status_url still gives the same result, so a broken endpoint costs you latency, not data.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume