Skip to main content
POST
/
v1
/
knowledge-bases
{
  "success": true,
  "knowledge_base_id": "knowledge_base_7a0682ce5fc02413",
  "unique_id": "1764105884537x291772143525964264",
  "name": "Product FAQ",
  "status": "in_progress",
  "total_sources": 2,
  "message": "Knowledge base created successfully",
  "powered_by": "Teli"
}

​
Overview

Knowledge bases enhance voice agents with additional context from URLs, documents, and custom text. Agents automatically retrieve relevant information during calls without any prompt changes needed. Use cases:
  • Product FAQs
  • Company policies
  • Support documentation
  • Pricing information
  • Technical specifications

​
Authentication

​
X-API-Key
string
required
Your Teli API key

​
Request Body

​
name
string
required
Knowledge base name (max 40 characters)
​
organization_id
string
required
Organization unique_id
​
user_id
string
required
User unique_id (creator)
​
urls
array
List of URLs to scrape and index. Max 500 URLs per knowledge base.
​
texts
array
List of text snippets. Each has title and text. Max 50 snippets per knowledge base.
​
auto_refresh
boolean
Enable auto-refresh for URLs (updates content every 24 hours). Default: false

​
Request Examples

curl -X POST "https://api.teli.ai/v1/knowledge-bases" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Product FAQ",
    "organization_id": "1762896364768x389173798861431550",
    "user_id": "1762896366429x599348279945132448",
    "urls": [
      "https://yourcompany.com/faq",
      "https://yourcompany.com/pricing"
    ],
    "auto_refresh": true
  }'

​
With Text Snippets

{
  "name": "Company Policies",
  "organization_id": "org_id",
  "user_id": "user_id",
  "texts": [
    {
      "title": "Pricing Policy",
      "text": "Our standard pricing is $99/month. Enterprise pricing available for teams over 50 users. Annual plans get 20% discount."
    },
    {
      "title": "Support Hours",
      "text": "Support available Monday-Friday 9 AM - 6 PM EST. Emergency support available 24/7 for enterprise customers."
    }
  ]
}

​
URLs + Text Combined

{
  "name": "Complete Knowledge Base",
  "organization_id": "org_id",
  "user_id": "user_id",
  "urls": [
    "https://yourcompany.com/docs"
  ],
  "texts": [
    {
      "title": "Quick Facts",
      "text": "Founded in 2020. 500+ customers. 99.9% uptime SLA."
    }
  ],
  "auto_refresh": true
}

​
Response

​
success
boolean
Whether creation was successful
​
knowledge_base_id
string
Unique ID of the created knowledge base. Use this to link to agents.
​
unique_id
string
Your platform’s unique ID (for internal reference)
​
name
string
Knowledge base name
​
status
string
Processing status: in_progress, complete, or error
​
total_sources
number
Number of sources added
​
message
string
Success message
​
powered_by
string
Platform identifier (“Teli”)
{
  "success": true,
  "knowledge_base_id": "knowledge_base_7a0682ce5fc02413",
  "unique_id": "1764105884537x291772143525964264",
  "name": "Product FAQ",
  "status": "in_progress",
  "total_sources": 2,
  "message": "Knowledge base created successfully",
  "powered_by": "Teli"
}

​
Processing Status

After creation, the knowledge base status will be in_progress. Processing includes:
  • Scraping URLs
  • Chunking content
  • Creating embeddings
  • Indexing for retrieval
Timeline: Usually 1-5 minutes depending on content size Status changes: 
⏳ in_progress → ✅ complete (ready to use)
⏳ in_progress → ❌ error (processing failed)
Check status: Use Get Knowledge Base endpoint

​
Limits

Per knowledge base limits:
  • URLs: Max 500
  • Text snippets: Max 50
  • Files: Max 25 (50MB each) - Use dashboard for file upload
  • Name: Max 40 characters
Create multiple knowledge bases to overcome these limits. Agents can link to multiple KBs.

​
Auto-Refresh

When auto_refresh is enabled:
  • URLs are re-fetched every 24 hours
  • Content automatically stays up-to-date
  • Useful for frequently changing documentation
Auto-refresh only applies to URL sources, not text snippets.

​
Next Steps

After creating a knowledge base:
  1. Wait for status to become complete (check via GET endpoint)
  2. Link to voice agent via knowledge_base_ids parameter
  3. Test calls to verify agent uses KB context
See: Link Knowledge Base to Agent
Enhance your voice agents with knowledge bases! 🚀