Assistants — Overview
An Assistant is the AI brain that replies to customers on a single channel for one organization. The dashboard page /dashboard/models/[modelId] manages exactly this record. The API mirrors every field on that page so AI agents can configure assistants end-to-end without human onboarding.
Key rules
- One channel → one assistant. A WhatsApp number, Instagram account, or Messenger page can be wired to at most one assistant. Connecting it to a new assistant automatically detaches it from the previous one.
- One channel per platform per org.The Sendiee model assumes one WhatsApp account, one Instagram account, and one Messenger page per org. You don’t need to pass IDs — just
{ "channel": { "platform": "whatsapp", "activate": true } }. - Channel can be left disconnected. Omit
channel(or passactivate: false) to create a draft assistant. Connect it later viaPATCH /v2.0/assistants/:modelId. - All edits go to history. Every create / update / toggle / channel change writes a versioned snapshot tagged
changedBy.source = "api"so the dashboard audit log surfaces API-driven changes alongside human edits. - Strict validation. Provider/model pairings, enum fields, and numeric ranges are validated locally. Failures return
422 ASSISTANT_VALIDATION_FAILEDwith adetails[]array. Fetch supported values fromGET /v2.0/assistants/options.
Endpoints
- GET/v2.0/assistants/optionsSupported providers, models, voices
- GET/v2.0/assistantsList with filters
- GET/v2.0/assistants/{modelId}Get one
- POST/v2.0/assistantsCreate
- PATCH/v2.0/assistants/{modelId}Partial update / channel activate
- POST/v2.0/assistants/{modelId}/toggleEnable / disable
- DELETE/v2.0/assistants/{modelId}Delete
- GET/v2.0/assistants/{modelId}/historyEdit history (last 10 versions)
- POST/v2.0/assistants/{modelId}/restoreRestore from history version
Tools API is coming
Tool configuration is being revamped — the Tools endpoints will ship after the new tools system is ready. For now, the assistant
tools array accepts the existing tool ObjectId strings.