Documentation
Three surfaces, one product. Drop the widget on your site, sign in to the operator inbox, talk to the REST API. Pick a starting point below.
Where to start
Sign up, install the widget, receive your first conversation in about five minutes.
Install with a single script tag. Configure language, position, identifying visitors, custom events.
How operators run conversations: assignments, internal notes, keyboard shortcuts, audit log.
Two checkboxes and a system prompt — that's the setup. Decide when the AI answers and how it should sound.
Build with us
Leadiosa exposes everything the dashboard does as a public API. You can route messages, manage contacts, drive the AI agent, and react to events via webhooks.
Bearer-token authentication, JSON in / JSON out, predictable resource-oriented endpoints.
HMAC-signed delivery for every event that matters: messages, conversations, contacts.
First-party bridges to Rocket.Chat plus a fully-documented REST API for building your own.
Feed the AI agent your docs. Pick an embedding provider per workspace; get cited answers back.
Conventions used in these docs
- Inline product names look like
this. Inline code, identifiers and field names look the same way. - Code samples default to bash + JavaScript. Tabs for other languages will be added as we cover more endpoints.
- Whenever a feature requires a specific plan, that requirement is called out in a tip box at the top of the relevant section.
- Anything marked “pending” means it is on the roadmap but not yet live. Send us a note via support@ if you depend on it.
Working assumptions
Throughout these docs we assume you have a Leadiosa workspace (sign up at /register if not), at least one operator account, and that you can edit the HTML of a site you control (for widget install).