Skip to main content

Overview

Knowledge bases are collections of documents and text that Sendora’s AI voice agents retrieve from in real time during a call. When a prospect asks “What’s your pricing?” or “Do you integrate with Salesforce?”, the agent searches the relevant KB and answers accurately instead of hallucinating. KBs support two source types via the API:
  • Text, paste in raw content (FAQs, product sheets, objection handlers)
  • URL, provide a web page URL and Sendora crawls and indexes it automatically
Four endpoints cover knowledge bases: List or get knowledge bases, Create knowledge base, Update knowledge base and Delete knowledge base. Sources are added, edited and removed through Update knowledge base.

Creating a knowledge base

Returns the created KB with an id you’ll use to add sources and assign it to agents.

Reading knowledge bases

A single knowledge base comes back with a sources array:
Possible source status values: pending, indexing, ready, error. Lists accept page and limit and report X-Total-Count, X-Page and X-Per-Page.

Adding sources

Add sources with add_sources on Update knowledge base. Each source is text or url.
Text is chunked, embedded and indexed within a few seconds. For a URL, Sendora crawls the page, strips navigation and footers, and indexes the main content. Crawling is asynchronous: read the knowledge base again and check each source’s status before the agent goes live.

Editing and removing sources

Read one source with GET /knowledge-bases?id=KB_ID&source_id=SOURCE_ID to get its content, its indexing_version and its last synced snapshot. expected_version is the version of the source you last read; if someone else has changed it since, the edit is refused so two edits cannot overwrite each other. Removing a source deletes it and all its chunks from the index; the knowledge base stays active. For a source that syncs from a connected app, restore_snapshots (a list of source_id and expected_version) puts the last synced copy back as the working copy, and accept_provider_updates makes a synced update the working copy. The steps run in this order: name and description, sources added, sources edited, snapshots restored, provider updates accepted, sources removed. If one fails, the earlier steps stay applied and the error lists them under applied.

Assigning a KB to a voice agent

A knowledge base becomes available to an agent when you assign it, with knowledge_base_ids on Update agent:
An agent can have several knowledge bases. During a call, the agent searches all assigned ones and picks the most relevant chunk. The list you send is the whole set: a knowledge base not in it is unassigned. The knowledge base itself is never deleted by this.

Deleting a knowledge base

Full KB lifecycle example