Build your own chat UI, send customer data into every conversation, react to chat events in your backend, and pull service results into your reporting.
Free 14-day trialNo credit card required24/7/365 support
Text is intuitive live chat software from the team behind LiveChat.com, HelpDesk.com, and ChatBot.com, products used by 30,000+ customers worldwide.
Start with the outcome, then pick the tool that gets you there. Each one covers a different part of a live chat API integration.
Build a custom chat UI in your web app when customization options matter and the standard widget is too limiting. Users start chats and send messages through an interface you create. Frontend developers own the look; Text handles routing, AI agents, and history.
Customer SDK docsKeep the standard widget and control it from your website. Show or hide it, set customer details, pass cart data, and react to widget events. One frontend developer can handle it.
JavaScript API docsGive your server direct access to chats. Read chat messages, send replies, transfer, tag, and manage agent status over REST or WebSocket. This is backend developer work.
Messaging APIs overviewLet Text tell your backend when something happens, such as a new chat or a tagged thread. Your endpoint decides what follows, like creating a CRM lead.
Webhooks docsPull chat volume, response times, ratings, and agent metrics into your BI software. Put support data next to sales data and see what conversations earn.
Reports API docsConnect AI assistants such as Claude or ChatGPT to Text through mcp.text.com. Assistants search tickets and chat transcripts under the signed-in user's permissions, and you don't need to write any code.
MCP setup guideIntegrations that pay off
Every integration helps close a sale, qualify a lead, or serve a customer faster.
Use Customer SDK when the standard widget
doesn't fit to make it truly yours.
Use the Chat Widget JavaScript API to pass account tier, cart value, or order status when a chat starts.
Use webhooks to send events from Text to your systems. The AI agent can call your APIs too.
Custom Skills can call any HTTP endpoint mid-conversation: check stock in your warehouse system, verify discount eligibility, or push a qualified lead into your CRM.
Built-in skills help in most common scenarios, like creating a Salesforce lead or a Slack alert when a chat ends. Webhooks and the Chat API cover the cases specific to your business.
Use the Reports API to pull chat volume, response times, and customer ratings into the dashboards your leadership reads.
“It was the easiest and most complex API I have ever used. I was able to extract everything by myself from the system to analyze the data. Such a powerful connection. The data was absolute gold.”
Start with one workflow and test it with real conversations before adding more. Most teams bring in a developer for part of the setup.
Write down the trigger, the data that moves, and the result you expect. Check ready-made integrations first. If a Marketplace app covers it, skip the custom build.
Live chat APIs use OAuth 2.1. A personal access token is the fastest route to a first request; OAuth tokens suit apps other users install. Request only the scopes you need and keep server tokens out of browser code.
Test with real data, including retries, duplicate events, pagination, and rate limits. After launch, watch API usage, token expiry, and failed requests.
Read getting started with the LiveChat API for background, then check the Text documentation for current endpoints.
Budget for the subscription, API usage, and developer time. Then give each integration only the access it needs.
API calls are included in your plan and reset each billing cycle: 10,000 a month on Essential, 20,000 on Growth. An extra 100,000 calls cost $29.50. Every request counts, including calls made with personal access tokens, except those that return a 500 error.
Agent tokens and customer tokens are separate and can't be swapped. Scopes are fixed when a token is created, so a read-only token can never send messages. Use HTTPS and rotate credentials. Copy only the customer data you need.
SOC2
PCI DSS – SAQ A
An API is the interface your code calls to read data or take an action, such as sending a message. An SDK wraps those calls into ready-made methods for one environment. Customer SDK is a live chat SDK for the browser; the Customer Chat API underneath gives developers direct control.
For most custom integrations, yes. Widget changes are frontend work. Webhooks and server-side chat automation need a backend developer. MCP setup needs no code, only a compatible AI assistant. If a Marketplace app already covers your use case, install it instead.
The subscription covers seats and features, billed per user per month. API usage is measured separately in calls per month, with an allowance in each plan and add-on packages when you need more. Developer time is the third cost to plan for.
Every request is authorized with OAuth 2.1 and limited by scopes set when the token is created. Agent and customer tokens are separate, data travels over HTTPS, and the MCP server enforces each user's existing permissions. On your side, store tokens securely and validate incoming webhooks.
No, your LiveChat plan stays the same. The features and capabilities on this page are part of Text and are available under Text pricing plans. They are not included in LiveChat plans, including legacy LiveChat subscriptions. Availability, limits, and pricing depend on your Text plan. If you’re on a LiveChat plan and want these features, you can move to Text.
