ClientContext
Opaque caller-supplied attributes attached to a conversation message.
Values are strings, including values such as "false". The schema allows at most 32 pairs, keys of at most 64 characters, and values of at most 1,024 characters. Keep the entire map well below 8 KiB: Travila also applies an encoded-size limit that includes field overhead and drops context that exceeds it. Short page identifiers and a few relevant values are preferable to a page dump; an oversized map is not automatically shortened.
Usage profiles
| Usage | Fields and validation |
|---|---|
| In requests | View fields |
| In responses | View fields |
| In webhook payloads | View fields |
In requests
API JSON uses JSON field names (camelCase).
| Field | Type | Presence | Meaning |
|---|---|---|---|
values | Map from string to string | Optional | Arbitrary client-supplied context for this message (e.g. page, referrer, device, in-app flow). Keys/values are opaque strings. Maximum properties: 32. |
Request validation
These rules apply when this value is supplied in a request. Request validation does not guarantee that response fields are present or satisfy the same rules.
| Applies to | Rule | Requirement |
|---|---|---|
values | Max Pairs | 32 |
values | Keys · Maximum length | 64 |
values | Values · Maximum length | 1024 |
In responses
API JSON uses JSON field names (camelCase).
| Field | Type | Presence | Meaning |
|---|---|---|---|
values | Map from string to string | Optional | Arbitrary client-supplied context for this message (e.g. page, referrer, device, in-app flow). Keys/values are opaque strings. |
Request validation
These rules apply when this value is supplied in a request. Request validation does not guarantee that response fields are present or satisfy the same rules.
| Applies to | Rule | Requirement |
|---|---|---|
values | Max Pairs | 32 |
values | Keys · Maximum length | 64 |
values | Values · Maximum length | 1024 |
In webhook payloads
Webhook JSON uses protobuf field names (snake_case).
| Field | Type | Presence | Meaning |
|---|---|---|---|
values | Map from string to string | Optional | Arbitrary client-supplied context for this message (e.g. page, referrer, device, in-app flow). Keys/values are opaque strings. |
Request validation
These rules apply when this value is supplied in a request. Request validation does not guarantee that response fields are present or satisfy the same rules.
| Applies to | Rule | Requirement |
|---|---|---|
values | Max Pairs | 32 |
values | Keys · Maximum length | 64 |
values | Values · Maximum length | 1024 |
Where used
| Reference | Relationship |
|---|---|
| Append a message without generating | POST /api/v1/llm/append-message |
| Send a message to a conversation | POST /api/v1/llm/send-message |
| Send a message and wait for the result | POST /api/v1/llm/send-message-sync |
| Withdraw your rating on a message | POST /api/v1/llm/delete-message-rating |
| Get full conversation state | POST /api/v1/llm/conversation-state |
| Rate an assistant message | POST /api/v1/llm/rate-message |
| Submit client-side tool results and wait for the next segment | POST /api/v1/llm/submit-client-tool-results-sync |
| llm.message_published | Webhook JSON uses protobuf field names (snake_case). |
| Message | Nested in model |
| Message | Nested in model |
| Message | Nested in model |
Download the public reference contract.
Document: DOC-API-MODEL-client-context.