API overview
Start here to understand the external AskAnyDocs API surface before using specific endpoints.
The API reference covers the external team API protected by bearer API keys.
External API groups
Base path:
/api/external
Current endpoints:
GET /api/external/account/statsGET /api/external/account/planGET /api/external/botsGET /api/external/bots/{id}/statsGET /api/external/bots/{id}/conversationsGET /api/external/bots/{id}/conversations/{conversationId}GET /api/external/bots/{id}/messagesGET /api/external/bots/{id}/messages/{questionId}
This API is read-only today. It is intended for retrieving bot metadata, conversations, and message history for the team associated with the API key.
Endpoint categories
Account endpoints
Use these endpoints to retrieve workspace-level information for the team connected to the API token:
- current usage and totals
- current plan and subscription state
- plan limits and enabled features
Bot endpoints
Use these endpoints to retrieve:
- bot metadata
- bot-level usage totals
- conversation lists and conversation details
- message lists and message details
Authentication model
The external API uses Authorization: Bearer <api_token>.
Response format
The external JSON APIs return standard JSON objects and arrays. For collection endpoints, the current shape is:
{
"items": []
}
Common HTTP status codes
| Status | Meaning |
|---|---|
200 |
Request completed successfully |
401 |
Missing or invalid bearer token |
404 |
Bot not found |
Before you build
Start with API authentication, then use the bots endpoint to discover the bot ids you want to work with.
Related articles
API authentication
Use bearer API keys to authenticate requests to the external AskAnyDocs team API.
External bots, conversations, and messages API
Use the external team API to list bots and retrieve conversation or message history for a team.
Knowledge sources API
Learn what the external API exposes today and why knowledge-source management is not part of the public API reference yet.