Skip to content
DaneshyarDocs
Sign in
  • Introduction
  • Quickstart
  • What is Daneshyar?
  • The Apps page
  • Inside an app
  • Workspace: files and chat
  • Sharing and members
  • Notes and dictation
  • Language practice
  • Appointment booking
  • Automations
  • The file reader
  • Your profile
  • Wallet
  • Customer chats
  • API keys
  • Authentication
  • Apps, workspaces, resources
  • Ingestion
  • Chat and sessions
  • Citations
  • Skills
  • Conventions
  • Workspaces
  • Resources
  • Chat
  • Skills
  • Errors
  • Customer support assistant
  • Internal knowledge base
  • Documentation chatbot
  • Academy tutor
  • Embedded widget
  • Widget configuration
  • Framework guides
  • Security
  • Troubleshooting
  • FAQ
  1. Docs
  2. Security and help
  3. FAQ

FAQ

Short answers about keys, the widget, answers and going live.

API keys

Two: a secret key for the REST API and a public widget key for the widget. Each can be replaced or deleted on the app page. To have two secret keys at once, make a second app. See API keys.

The widget key: on the app's page, you can copy it at any time. The secret key is shown only once — if you lost it, press Regenerate under Secret key and use the new one.

Yes, each key separately. On the app page in the console, press Regenerate for a new key or Delete to switch it off. The old key stops working at once. See Security.

The secret key: in a server environment variable or a secret manager, never in Git. The widget key: it is public anyway, so a front-end variable is fine.

The widget

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.

No. The widget has no events or callbacks. Use inline mode to show and hide the chat with your own code. See Bubble and inline.

Answers

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.

docs.faq.items.memory.a

Going live

The account that owns the app. Each answer is paid from its wallet, 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 limits uploads to 60 an hour and retries to 30 an hour; other calls have no 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.

PreviousTroubleshooting

On this page

  • API keys
  • The widget
  • Answers
  • Going live

Every example on this site runs against the live API. If one doesn't, tell us — that's a bug in the docs.

ServicesAboutTalk to us