Skip to main content
The MITHUNAI API gives your software everything the console can do: conversations and streaming answers, assistants, knowledge and the connections it is read with, widget embeds, members and invitations, analytics and branding. Managing API keys and people takes a signed-in console session rather than an API key; each page says which credential it accepts.

​
The resources

​
Base URL

If your organisation uses a different MITHUNAI host, use that host with the same /mithunai/api/v1 path. Examples in this reference use two environment variables:

​
Conventions

​
Where to call it from

Call the API from your servers. Apart from the widget endpoints, it does not accept cross-origin requests from browsers, and API keys must never be exposed to a browser.

​
Versioning and stability

The API is versioned in its path. Within v1:
  • Endpoints are not removed and do not change meaning.
  • Error code values are not renamed.
  • Streaming event names are not renamed, and no new terminal event is added.
  • New optional fields and new non-terminal event types may be added.
Your client must ignore fields and event types it does not recognise.

​
Try it

Every endpoint page has an interactive playground. Enter your MITHUNAI API key as the bearer token to send real requests to app.mithunai.com from the page.

Quickstart

Your first cited answer, end to end.

Ask a question

The core endpoint.
Last modified on November 7, 2026