---
title: "Diagnose why a chatbot does not answer"
method: GET
path: "/api/v1/chatbots/{id}/diagnose"
---

# Diagnose why a chatbot does not answer

`GET /api/v1/chatbots/{id}/diagnose`

## Request

- Base URL: `https://smartwebchat.eu`
- URL: `https://smartwebchat.eu/api/v1/chatbots/{id}/diagnose`
- Auth: HTTP bearer

Read-only; a read key is enough. findings lists { code, severity, remedy, details } — codes and remedies are in the error catalog. ok is false when a finding has severity error (visitors get no answer); complete is false when a check could not be read (CHECK_FAILED).

## Path parameters

- `id` string, required

## Response `200`

Diagnosis

- Diagnosis
  - `chatbotId` string, required
  - `ok` boolean, required
  - `complete` boolean, required
  - `findings` object[], required
    - `code` 'access_inactive' | 'message_limit_reached' | 'credits_exhausted' | 'provider_unavailable' | 'provider_not_allowed_for_healthcare' | 'origin_rejected' | 'knowledge_source_error' | 'check_failed' | 'origin_allowlist_empty' | 'knowledge_none_ready' | 'no_web_conversation', required
    - `severity` 'error' | 'warning' | 'info', required
    - `remedy` string, required
    - `details` object

## Other responses

- `401`: Invalid or missing API key
- `404`: Chatbot not found (also for a chatbot of another account)
- `429`: Rate limit exceeded: 600 requests per minute per account across all /api/v1/ routes. Wait for the seconds given in Retry-After (60) and retry.

---

[API](https://skmtc.dev/smartwebchat/apis/smartwebchat-api.md) · [All operations](https://skmtc.dev/smartwebchat/apis/smartwebchat-api/llms.txt) · [OpenAPI document](https://skmtc.dev/smartwebchat/apis/smartwebchat-api/revisions/1b052502dacb?raw)