Book a demo Start free
A developer working at two monitors in a bright office

Developers

Build Texa into your own product

Your app opens a conversation, sends what the customer said and shows Texa’s reply. Actions run in your systems, and webhooks tell you everything as it happens.

Start free Book a demo

Photo: Zayed Hossain

Your first conversation

Two requests to your first reply

Open a conversation with your own id for the customer, then send each message. Every answer carries Texa’s events in order: a reply to show, an action for your systems, a handover to people, or the end of the conversation.

  • Base URLhttps://api.texadesk.com/v1
  • KeysTest keys reach your sandbox, live keys reach real customers. A key is shown once.
  • Safe to retrySend the same message_id or Idempotency-Key again and you get the first answer back. Nothing runs twice.
The five-minute quickstart All the documentation, at developers.texadesk.com
Terminal 
curl https://api.texadesk.com/v1/conversations \
  -H "Authorization: Bearer $TEXA_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: open-user-1842" \
  -d '{"channel": "web", "customer_ref": "user-1842", "first_name": "Tolu"}'

curl https://api.texadesk.com/v1/conversations/$CONVERSATION_ID/messages \
  -H "Authorization: Bearer $TEXA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message_id": "msg-551", "text": "My transfer of 80,000 has not arrived"}'

Your website and app

Texa in your own website and app

One script tag, or a component in your app. Visitors get answers from your knowledge. Once they sign in, the same chat knows who they are and works in their account through your systems, and your team sees every chat in Texa Desk.

  • In their accountTexa looks things up, makes changes with the customer’s yes, sends receipts and statements, takes them to the right page and fills in forms.
  • Your code stays yoursYou add one route on your server that says who is signed in, and choose in Texa Desk what Texa may do. Your own API decides what each customer may see.
  • Your team, liveEvery chat shows in Texa Desk as it happens, with what the customer is typing, card numbers and PINs hidden.
How to add it
A young man on a sofa reading his phone
Lagos. Photo: Omotayo Oluwatosin

Everything you need to run it in production

Keys, limits, logs and webhooks are managed in Texa Desk, under Texa AI → Developers.

  • Rate limitsA clear 429 with Retry-After when you go over, per key.
  • Request logEvery call with its key’s hint and result. Bodies are never stored.
  • Signed webhooksEvery event signed with your secret, retried with backoff, with a delivery log, a resend button and a test event.
  • Events feedEvery event in order on GET /v1/events, with a cursor, as the complete record.
  • OpenAPIA full reference and an OpenAPI document for your own tools.
  • StatusEvery part checked each minute, with the last 90 days, on the status page.
  • The Texa Desk APIConversations, contacts, tickets, reports and settings, webhooks, your own bots and your own panels beside each conversation.

SDKs and widgets

Published SDKs, one contract

Each SDK is a thin client over the same API, with an action handler that runs Texa’s requests with your functions and a check for webhook signatures. All of them pass the same contract tests, and their source is public.

  • Install todaypip install texa, npm install @texadesk/sdk, composer require texa/texa-php, and Go and Swift from GitHub. Java and Flutter are coming soon.
  • WidgetsA chat and voice widget for websites, and @texadesk/react-native for apps.
  • No keys in the browserYour server creates a short session for one customer, valid only on the websites you list.
The SDKs
A young man smiling at his desk with a laptop
Photo: Abdullahi Sow

Actions and handover

Your systems do the work. Your team takes the hard cases.

Texa asks, your code answers, and nothing Texa says depends on a guess.

  • Actions in your systemsA ready-made connector (Paystack, Flutterwave, Shopify…), your API from its OpenAPI file or documentation page, or your own server. Writes need the customer’s yes first.
  • Handover your waySend conversations that need a person to your own system by webhook, or into a Texa Desk inbox.
  • Voice in your appYour server gets a single-use token, and your app talks to Texa directly.
  • Texa as an MCP serverLet your own AI tools ask what customers are saying, read transcripts and pull reports, with citations.
  • Your MCP servers as actionsConnect an MCP server and its tools become actions, with the same rules as any other.
  • A free sandbox2,000 requests a month on test keys, with fixtures you set for each action.
A young man smiling at his desk with a laptop

Get a test key and send your first message

Create a free account, open Texa AI → Developers, and make a test key. The sandbox is free for 2,000 requests a month.

Start free Book a demo

Photo: Abdullahi Sow