ElevenLabs Flows API states vs Sume job status and webhooks

The ElevenLabs Flows APIs are asynchronous: a generation reports pending, generating, completed or failed, and a request can include a webhook target. On Sume the equivalent is a job: submit with mode: "async", poll GET /v1/jobs/:id/status until it is terminal, or pass webhook_url and wait for a terminal event.

ElevenLabs details are from its August 17, 2026 changelog. Sume behavior is from Jobs and results and Webhooks, read 2026-10-01.

What does the Flows API add on the ElevenLabs side?

The entry says the new asynchronous APIs create, list and retrieve video, image and speech generations. It names the four states above and a webhook target for completion events. It also adds asset APIs so a generation can reference an uploaded asset or an earlier generation.

How do the states map to a Sume job?

Sume's docs call queued and processing normal non-terminal states and tell clients to poll until terminal: true. The table is a reading aid, not a one-to-one contract.

Does a Sume sync request wait for the job?

Only up to a budget. The OpenAPI text says the wait is bounded by wait_timeout_seconds (max 30), and that bounds the HTTP request, not the job. When it runs out, poll status_url instead of resubmitting. For audio, /result returns 409 job_not_completed until result_ready is true.

What does a Sume webhook tell me?

Terminal events only: job.completed, job.failed and job.canceled. There are no progress or partial deliveries, so a generating-style intermediate state is something you poll for. Keep a polling fallback next to the webhook.

On cost: every Music Router model charges the fixed Music price per audio generation, per Music Router. A sibling post covers ElevenLabs Flows webhook targets.