Knowledge sources API

Knowledge sources define what the bot can answer from, but today knowledge-source management routes are dashboard routes, not part of the external public API.

Current external availability

At the moment, external API integrations do not have public endpoints for:

• creating website resources
• creating sitemap resources
• uploading files
• deleting knowledge sources
• triggering indexing from a bearer-token integration

Those flows currently exist inside internal application routes under /api/app/... and are intended for the dashboard UI.

What you can do today

Today, the public external API is focused on:

• reading bots
• reading conversations
• reading messages
• retrieving read-only bot, conversation, and message data

Recommended integration approach

If you need to manage knowledge sources programmatically right now, the practical approach is:

1. manage bot content through the dashboard
2. use the external API for reporting or downstream analytics
3. use the website widget flow separately from the external bearer-token API

Planned documentation boundary

This section exists so external API users do not confuse internal dashboard routes with supported bearer-token integration endpoints.

Related articles