Conversations (mobile only)
Not a public API. The conversation endpoints exist only for Syntic’s own mobile apps. They are not available to API keys, are not covered by the versioning policy, and can change without notice. This page exists so that nobody builds on them by mistake.
Syntic Mobile keeps a person’s chat history on the server so it is the same on every device. It reads and writes that history through private /v1/conversations routes that accept only a mobile sign-in token issued to the syntic-mobile app (see Sign in with Syntic).
What happens if you call them
| Credential | Result |
|---|---|
An inference key (sk_live_...) | 403 permission, code not_available_for_api_keys |
| An Admin key | 403 permission, code not_available_for_api_keys |
| A sign-in token from any app other than Syntic Mobile | 403 permission, code client_not_allowed |
What to use instead
| You want to | Use |
|---|---|
| Keep a multi-turn chat in your own app | Store the messages yourself and send them with each chat completion; see Chatbot memory. |
| Have Syntic keep the conversation server-side | Agent sessions hold the history, tools and state for you. |
| Review members’ chats for compliance | The Compliance API, Enterprise plans only. |
Was this page helpful?