Skip to main content
Assistants are the core conversational entities in IllumiChat. Each assistant has its own system prompt and its own knowledge base for retrieval-augmented generation (RAG). All assistants use the same AI model.
These endpoints require a signed-in browser session, not an API key. There is currently no API-key accessible Assistants API — a workspace API key (Authorization: Bearer ...) is only accepted on the /api/v1/* endpoints (contacts, messages, tickets). See API Overview for the two surfaces.

Assistant Configuration

Visibility Levels

visibility governs access to the assistant in the internal Chat workspace only — it has no effect on the embeddable widget. Widget access is controlled by the widget’s own isEnabled flag (part of the assistant’s widget configuration, not the assistant object — see the Widget endpoints), independent of visibility.

List Assistants

Returns assistants accessible to the authenticated user within a workspace. workspaceId is required.
Response 200 OK

Create Assistant

Creates a new assistant in the workspace. Requires owner or admin role.
Response 201 Created with the full assistant object.

Get Assistant

Retrieves a single assistant by ID.
Response 200 OK with the full assistant object including instructions, temperature, maxTokens, visibility, welcomeMessage, and timestamps.

Update Assistant

Updates an assistant’s configuration. Requires owner or admin role. All fields are optional; only provided fields are updated.
Response 200 OK with the updated assistant object.

Delete Assistant

Permanently deletes an assistant and all its conversations. Requires owner or admin role.
Response 204 No Content
Deleting an assistant permanently removes all associated conversations, widget sessions, and SMS configurations. This action cannot be undone.

Knowledge (RAG)

Each assistant owns its own knowledge base, and it is managed in the app rather than over the public API — there is no endpoint for connecting a separate document collection. When a customer sends a message, the assistant searches its own static sources for relevant context and includes it in the prompt.
Static sources (files, websites, text, Q&A) are chunked, embedded, and stored in a vector database (Pinecone) under a namespace dedicated to that assistant’s knowledge base. Realtime sources (Shopify, WooCommerce, spreadsheets) are read live at question time and are never indexed. See Knowledge Base.

SMS Configuration

Assistants can be configured to send and receive SMS messages via Twilio. Each assistant has its own Twilio credentials using a bring-your-own-key (BYOK) model.

Get SMS Config

Requires admin role or above.
Response 200 OK

Create or Update SMS Config

Use POST to create the configuration and PATCH to update an existing one. On PATCH every field is optional; only the fields you send are changed.

Delete SMS Config

Response 204 No Content

Test SMS Credentials

Validates the provided Twilio credentials without saving them.
Response 200 OK

List SMS Sessions

Returns the assistant’s SMS conversations, most recent first.
There is no per-assistant SMS analytics endpoint. For message volume broken down by channel, use GET /api/analytics/channels.
After configuring SMS, set the Twilio webhook URL to the value returned in the webhookUrl field of the SMS config response. This URL handles inbound messages from your customers.