Docs chat API and chat hooks

Authenticate with the project API key#

Every call sends the project's API key as a bearer token.

1. Open Settings ▸ Domain & API and find the API Key card.
2. Copy the key. It starts with dbk_.
3. Send it on each request as Authorization: Bearer dbk_….

Reset key on the same card issues a new key and revokes the old one at once.

Ask a question#

One call returns one finished answer as JSON; the endpoint does not stream.

{
  "answer": "Rotate a key from the API keys page … [ref:guides/api-keys|API keys||Rotate a key]",
  "refs": [
    {
      "pagePath": "guides/api-keys",
      "pageTitle": "API keys",
      "headingText": "Rotate a key",
      "headingId": "rotate-a-key"
    }
  ],
  "follow_up_questions": [
    "Do old keys stop working right away?",
    "Can I have two keys at once?",
    "Where do I see when a key was created?"
  ]
}

answer is markdown. With Semantic Search on, it carries an inline [ref:…] marker after each cited sentence and refs lists those pages, headingId being the anchor on the rendered page. With it off, refs comes back empty.

Call it from your server#

curl -X POST https://docsbook.io/api/v1/chat \
  -H "Authorization: Bearer $DOCSBOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question": "How do I rotate an API key?"}'

const res = await fetch("https://docsbook.io/api/v1/chat", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.DOCSBOOK_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ question: "How do I rotate an API key?" }),
})
const { answer, refs, follow_up_questions } = await res.json()

An API call is billed like a reader's question.

• Balance — it draws on your balance by the tokens it used, at the price shown on AI Visitors Chat Model; there is no separate API quota.
• Your own key — answers made with Your own AI API Key are billed by your provider.
• Events — each call fires chat_question_asked, plus chat_no_answer when the chat didn't know, so alerts and trigger cards see API questions too.

Chat hooks: your code around every answer#

Chat hooks are three HTTPS URLs of yours that Docsbook calls around every answer — on your site, over this API and through ask_project_docs.

tool_calls lists the pages the answer read, one { "tool": "read_page", "path": … } each. Every hook request is a POST with a JSON body and a 5-second timeout.

What the pre-hook can return#

The pre-hook can stop a question or add to it. Reply with one of these, or with nothing.

{ "block": true, "reason": "Contract pricing comes from your account manager." }

{ "inject_context": "This reader is on the Enterprise plan, region EU." }

• block: true — stops before search and the model, so nothing is billed. The chat on your site shows "Sorry, I could not answer that."; the API returns 502 with blocked_by_hook and your reason.
• inject_context — added to the chat's instructions for this one question.
• Anything else — a non-2xx status, a body that isn't JSON, or no reply within 5 seconds, and the chat answers as if no hook were set.

Set and test hooks#

Set hooks from your agent with set_chat_hooks; there is no form for them in the panel. URLs must be https://, and an empty string clears one.

{
  "workspace_id": "acme/docs",
  "pre_url": "https://api.example.com/docsbook/pre?token=YOUR_SECRET",
  "post_url": "https://api.example.com/docsbook/post?token=YOUR_SECRET"
}

• Test — test_chat_hook with hook_type set to pre, post or streaming posts { "test": true, … } to that hook and returns its status code, latency and the first 500 characters of its reply.
• Over REST — POST /api/v1/set_chat_hooks takes the same pre_url, post_url and streaming_url with your API key.
• Not a hook — the chat's other URL, the Call To Action URL, is a link the chat offers readers.

Next steps#