Can I continue a Sume Agent Completion with thread_id?
Not yet. Every Agent Completion runs in a fresh thread, so a follow-up call cannot reuse thread_id. Pass earlier results back in the next request instead.
Not yet. The Agent Completions docs list continuing a prior thread with thread_id under not available yet, and say every completion runs in a fresh thread. Send what the follow-up needs in the next request.
Everything here is from Agent Completions and Run webhooks, read 2026-09-30.
What is thread_id in the receipt for?
The receipt returns a thread_id such as thr_... so you can tell which thread the run used. The docs present it as information, not as a request field to resume from.
What can I carry into the next call?
| Option | Note from the docs |
|---|---|
instruction / messages | Restate context as system or user text; no assistant turns |
input | Caller data written whole to a file; treated as data, not instructions |
attachments | Up to 30 images |
output_schema | Bind output to your schema, then feed output forward |
How do I pass the earlier output forward?
Read output from the completed run and put it into input of the next request. Use a new Idempotency-Key, because reusing a key with a different payload returns 409 idempotency_conflict.
curl -sS -X POST "https://api.sume.com/v1/agent/completions" \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: follow-up-002" \
-d '{
"instruction": "Write three shorter variants of the headline in input.",
"input": { "headline": "Aurora Headphones, all day" },
"generation_spend_cap_usd": 2
}'Do Format runs behave differently?
The run webhooks page notes that continuing a Format run starts a new run, which delivers its own single terminal webhook under the new run id. That page is about Formats, not Agent Completions.
Are completions shared with a team?
Not yet. The docs list team-owned threads under not available yet: Agent Completions are user-owned. Service-account keys cannot create them either and fail with 403 insufficient_scope and a details.reason of service_account_agent_completions_unsupported. Keys created before Agent Completions shipped lack the agent_completions scopes, and scopes cannot be added to an existing key.
Sources
Related posts
More in Developers
- Get the rendered MP4 back from a video editing API job
Descript's API lists no rendered file download without publishing. In Sume, a finished timeline_render job result carries video_url; here is the poll flow.
- 429 enforced_spend_limit_reached: why retrying never works
A 429 with no retry-after can be a monthly spend cap, not a rate limit. What Anthropic's page says, and how Sume separates 402, 429 rate_limited and queue_full.
- Face swap API: quality has no default, unlike avatar videos
Avatar videos default to plus when quality is omitted. Sume's Beta face swap has no default: quality is required and takes standard, plus or max.
- FLUX image URL expires after 10 minutes: what Sume returns
Black Forest Labs says generated FLUX image URLs expire after 10 minutes. Sume returns Sume-hosted signed URLs; here is how to fetch and keep the file.
Written by Sume