API

Every workspace has one public API key, used to authenticate calls to Docsbook's REST API from your own backend. Today the API exposes one capability: exporting your workspace's AI docs-chat as a plain REST endpoint — the same grounded-answer engine that powers the AI chat widget on your published docs site, so you can build your own support bot, Slack integration, or CLI on top of it.

Getting your API key#

Open Integrations — reachable from your avatar dropdown in the /chat input, or your profile dropdown in the admin panel. From there you can view (masked or revealed), copy, or reset your key.

There is one live key per workspace. Resetting immediately revokes the old one — there is no key history, so update any callers before you reset.

Authentication#

Every request is authenticated with a Bearer token — your workspace's API key.

Authorization: Bearer dbk_<your_api_key>

Keep your key secret — it grants full access to your workspace's AI chat, billed against your workspace's AI token budget (the same budget the docs-chat widget uses; there is no separate API-only quota).

POST /api/v1/chat#

Ask a question against your workspace's documentation and get back an answer grounded in your own pages.

Request body#

Example#

curl -X POST https://docsbook.io/api/v1/chat \
  -H "Authorization: Bearer dbk_<your_api_key>" \
  -H "Content-Type: application/json" \
  -d '{"question": "How do I set a custom domain?"}'

Response#

{
  "answer": "You can set a custom domain from the Branding tab...",
  "refs": [{ "pagePath": "design/domains", "title": "Custom Domains", "heading": "Setup" }],
  "follow_up_questions": ["What SSL certificate is used?", "Can I use a subdomain?"]
}

Errors#