Introduction
Lane.Chat is a hosted customer-support platform. You get an AI-assisted chat widget, a shared multichannel inbox, and a set of developer surfaces to wire it into your own product: a browser JavaScript API, a REST API, native iOS and Android SDKs, and outbound webhooks.
Lane.Chat is SaaS-only. There is no self-hosted backend to run — every integration talks to the official Lane.Chat cloud.
What you can build
- Embed live chat on any website or single-page app with one script tag.
- Identify your visitors and push custom attributes so agents see who they are talking to.
- Reach customers on their channel — the same conversation can flow through the web widget, Telegram, WhatsApp, Slack, or email.
- Send rich messages — cards, carousels, buttons, forms, links, and markdown — driven by no-code Flows or your own backend.
- React to events through webhooks, or stream messages live over WebSocket.
- Ship native mobile support with the iOS and Android SDKs.
Key identifiers
You will see two application identifiers throughout these docs:
| Identifier | Where it is used | Notes |
|---|---|---|
app_pub (app key) | Widget, native SDKs, public endpoints | The public application key, e.g. app_1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d (app_ + 32 hex). Safe to ship in client code. It is the value you put in data-app-key / window.laneChatAppId. |
The widget and the native SDKs never hold your account password or any signing key — they authenticate visitors with a short-lived visitor JWT that the server issues on session init.
Domains
| Host | Purpose |
|---|---|
https://cdn.lane.chat | Widget script (/js/widget.js) and the hosted widget host page (/widget.html). |
https://api.lane.chat | Public REST API. Public URLs are of the form https://api.lane.chat/v1/.... |
https://dash.lane.chat | Dashboard and the base host the native SDKs call. |
Where to go next
- New to Lane.Chat? Start with the Quickstart.
- Embedding in a SPA or inline? See Installation.
- Building a backend integration? Jump to the REST API and Webhooks.