Authorizations
API key authentication using Bearer scheme
Body
User identifier: The UID of the user to create the iframe for. This is used to track usage and thread history. This can be anything you want, but it must be unique. We recommend using a user ID or email.
1
List of Source/Connection IDs: The IDs of the sources/connections to use for the iframe. This is used to determine which sources/connections the user will have access to in the chat.
Token lifetime in seconds (60-3600, default: 900)
60 <= x <= 3600
Array of session-specific (stateless) knowledge base entries. These temporary entries apply only to this iframe instance and do not persist. They work alongside any persistent (stateful) entries previously created through /api/v1/knowledge-base/ for your connection IDs.
Array of session-specific (stateless) reference query objects (e.g., {"title": "...", "query": "..."}). These temporary queries apply only to this iframe instance and do not persist. They work alongside any persistent (stateful) queries previously created through /api/v1/reference-queries/ for your connection IDs.
Model to use for generated threads
o3
- o3o4-mini
- o4-minigpt-4.1
- gpt-4.1gpt-5
- gpt-5sonnet-4
- sonnet-4
o3
, o4-mini
, gpt-4.1
, gpt-5
, sonnet-4
Response mode: "full" shows all details, "basic" hides technical details
full
- fullbasic
- basic
full
, basic
Theme configuration to apply to the iframe (theme_mode, custom_css_vars, start_message)
ID of the theme to apply (mutually exclusive with theme)
Show the chat sidebar inside the iframe (default: true)
Optional per-uid rate limits