Ragbee is an API-first platform: every surface we ship — web chat, voice, Telegram, Discord — is a thin runner over the same authenticated API. Yours can be the next one. Ask questions against your workspace documents, build bots on the chatbot registry, route your channel through the capability engine, and manage sessions yourself.
One call to answer a question from your documents — with citations:
curl -X POST https://ragbee.ai/api/v1/chat/ \
-H "Authorization: Bearer $RAGBEE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tenant_id": 1,
"workspace_id": 1,
"question": "What is our PTO accrual policy?",
"top_k": 5
}'
The response returns the answer plus the document sources it was drawn from. Follow-up questions work naturally — retrieve conversation context per channel and pass it along.
| Endpoint | What it does |
|---|---|
POST /api/v1/chat/ | Ask a question against a workspace's documents; returns a cited answer. |
POST /api/v1/chatbots/resolve/ | Resolve a bot by platform + endpoint; returns tenant/workspace/bot config for your runner. |
POST /api/v1/chatbots/context/ | Fetch recent conversation transcript for context-aware replies. |
POST /api/v1/chatbots/messages/ingest/ | Store conversation messages (automatically PII-redacted at rest). |
POST /api/v1/chatbots/rewrite-reply/ | Shape an answer for your channel (voice-friendly, chat-friendly). |
POST /api/v1/support/shipping/bot-lookup/ | Capability routing for channel runners: personal-data lookups, package tracking, or knowledge — one endpoint. |
POST /api/v1/support/shipping/bot-session/end/ | End an authenticated session (e.g. when a call hangs up). |
Every request carries a Bearer API key. Keys are created in your dashboard, stored hashed, scoped to your tenant, and usage-tracked. Tenant isolation is enforced on every route — a key can never reach another tenant's documents, conversations, or data.