Skip to main content

​
Continue work across runs

conversation_id lets your backend continue a CREAO-hosted conversation across async and realtime runs. If you omit conversation_id, CREAO creates a new conversation and returns its ID in the create-run response.
Store that conversation_id in your own application database when you need future runs to share context.

​
Follow-up run

​
Ownership

Conversation IDs are account-scoped. A provided conversation_id must belong to the same CREAO account as the Account API key.

​
Workspace binding

Optional workspace_id on POST /v1/runs and POST /v1/realtime/runs binds the conversation to a personal workspace so the agent can read workspace files.
  • New conversations store the provided workspace_id.
  • Follow-up runs omit workspace_id to inherit the bound workspace.
  • An unbound conversation can be bound the first time you send workspace_id.
  • Sending a different workspace_id than the one already bound returns 409 WORKSPACE_MISMATCH.
Invalid or cross-account conversations return:
conversation_id is opaque. Do not parse it or treat it as your own end-user ID. Store your own user or workflow mapping next to the CREAO conversation ID.