Sume webhook vs async polling vs sync vs subscribe: pick a mode
Sume has four communication modes: async, sync, webhook and subscribe. Webhook is best for servers, but keep the poll fallback for lost deliveries.
Sume documents four communication modes for jobs: async, sync, webhook and subscribe (read 2026-10-06 in the webhook docs). Webhook suits a server that needs a notification at a terminal state.
Which should I choose?
Use webhook for server pipelines, and keep polling in place because delivery is an optimization, never the only recovery path.
What should I do in practice?
Mix webhook and polling for resilience.
- Webhook for backend pipelines.
- Poll
status_urlfor lost events. - See the Jobs and results page for the others.
Sources
Related posts
More in Developers
- SvelteKit +server.ts endpoint for an AI video webhook: request.text()
A SvelteKit POST handler reads request.text(), verifies Sume's HMAC over timestamp.body with node:crypto and returns 401 for bad or missing signatures.
- Swap the AI image model without a redeploy: JSON config hot reload
Read the Sume image model id from a JSON file that reloads when it changes, so a gpt-image-1 shutdown fix is a one-line edit with no deploy. Python, stdlib.
- Sweep for missed Sume webhooks: list queued and processing jobs
A webhook is an optimization. Run a periodic sweep over GET /v1/jobs with status=queued and processing, then compare against your own records and re-check each.
- Test a Sume poll loop without waiting: inject sleep, assert delays
Unit test a job poll loop in milliseconds by injecting the fetch and the sleep. Assert that next_poll_after_seconds is obeyed and the 20-minute deadline holds.
Written by Sume