FAQ
Short answers about keys, the widget, answers and going live.
One. The key is made with the app and stays the same for the app's whole life. To get a second key, make a second app. See API keys.
In the console, on the app's page, in the API key card. You can copy it from there at any time.
Not yet. If a key leaks, contact us and we will replace it. See Security.
For server calls: in a server environment variable or a secret manager, never in Git. For the widget: the key is public anyway, so a front-end variable is fine, but use a separate app for it.
Yes: the language, theme, accent color, title, subtitle, first message, button text, corner and distance. See Widget configuration. You cannot add your own CSS, because the chat runs in an iframe.
No. A conversation lasts while the page is open. Nothing is saved in the visitor's browser, and visitors cannot see each other's chats.
Not with an option. The widget always uses every ready document in its workspace. To limit it, make a workspace with only those documents and point the widget at it.
Yes, one per widget. Each page can show one widget, so use a different snippet with a different data-workspace-id on each part of your site.
Not yet: the widget has no events or callbacks. Inline mode lets you show and hide the chat with your own code. See Events and callbacks.
On purpose. It answers only from your documents, so it doesn't make up answers. If a question is not covered, it says so.
Each answer lists the documents it used, and numbered markers in the text point to the exact passage. See Citations.
The widget's own text comes in Persian and English (data-locale). Answers come from your documents, so questions work best in the language your documents are written in.
The account that owns the app. Each answer uses credits, the same as a chat in the console. Visitors pay nothing and never see billing messages.
For the widget: 20 questions an hour per IP address, 500 a day per app, and 60 loads an hour per IP address. The REST API has no rate limit yet. See Limits and costs.
Use two apps, each with its own key, workspace and allowed domains. Keep the ids in environment variables, so the same code works in both.
Yes. The REST API lives under /v1. A breaking change will come as a new version, and these docs describe /v1.