Texa AI in your product

Knowledge

Add documents to what Texa AI answers from, through the API, with a person's approval.

Texa AI answers only from knowledge your team approved: documents, web pages and help centre articles. Most companies add knowledge in Texa Desk (Texa AI → Knowledge), where they can also read a whole website (up to 10,000 pages from its sitemap: the first 30 at once, the rest in the background) or connect their help centre. The API is for keeping knowledge in step with a system of yours: a product catalogue, a price list, a policy library.

Add a document

Shell

curl -X POST https://api.texadesk.com/v1/knowledge/documents \
  -H "Authorization: Bearer $TEXA_API_KEY" -H "Content-Type: application/json" \
  -d '{"title": "Transfer limits", "kind": "policy",
       "body": "Daily transfer limits: Tier 1 accounts ₦50,000; Tier 2 ₦200,000; Tier 3 ₦5,000,000.",
       "uploaded_by": "policy-sync"}'

A document is not used until a person approves it in Texa Desk. This is deliberate: what Texa AI tells customers is your company's word, so a named person says yes to it. Approvers see the document under Texa AI → Knowledge, with who sent it (uploaded_by).

See what's there

Shell

curl https://api.texadesk.com/v1/knowledge/documents -H "Authorization: Bearer $TEXA_API_KEY"

Each document has its approval state, so a sync job can tell what is waiting for a person.

Writing knowledge that works

One topic per document, with a title a customer would recognise.
Facts, not marketing: numbers, steps, conditions, exceptions.
Say what's not possible, too ("We don't deliver outside Lagos and Abuja"). Texa AI says it doesn't know rather than guess, so a missing fact becomes a handover.
What changes often (balances, order states) is not knowledge: it is an action.