> ## Documentation Index
> Fetch the complete documentation index at: https://docs.creao.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Conversations

> Continue CREAO Developer API work with opaque conversation IDs.

## 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.

```json theme={null}
{
  "run_id": "11111111-1111-4111-8111-111111111111",
  "status": "pending",
  "agent_id": "00000000-0000-4000-8000-000000000000",
  "conversation_id": "22222222-2222-4222-8222-222222222222"
}
```

Store that `conversation_id` in your own application database when you need future runs to share context.

## Follow-up run

```bash theme={null}
curl -X POST https://developer.creao.ai/v1/runs \
  -H "Authorization: Bearer cr_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_id": "00000000-0000-4000-8000-000000000000",
    "conversation_id": "22222222-2222-4222-8222-222222222222",
    "input": { "follow_up": "Turn that into a slide outline" }
  }'
```

## Ownership

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

Invalid or cross-account conversations return:

```json theme={null}
{ "error": "CONVERSATION_NOT_FOUND" }
```

<Note>
  `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.
</Note>