---
title: "Get chatbot training status"
method: GET
path: "/chatbot/status/{chatbotId}"
tags: ["Chatbot Operations"]
---

# Get chatbot training status

`GET /chatbot/status/{chatbotId}`

## Request

- Base URL: `https://api.chat-data.com/api/v2`
- URL: `https://api.chat-data.com/api/v2/chatbot/status/{chatbotId}`
- Auth: HTTP bearer

Get the current training progress of the chatbot.

## Path parameters

- `chatbotId` string, required

## Response `200`

Successful response.

- ChatbotStatusRes
  - `status` 'success', required: The overall status of the chatbot.
  - `progress` number, required: The training progress of the chatbot. For the pre-trained medical chat models, the progress is set to 100 when the chatbot is created. For chatbots trained on your own data, it starts at 0.

## Other responses

- `400`: An unexpected error occurred while processing the request; `message` contains the error.
- `401`: Authentication failed: the `Authorization` header is missing or not in the `Bearer <key>` format, the API key does not exist, its workspace is unavailable or has no owner, or the workspace's plan does not include API access. `message` says which.
- `403`: The API key cannot access the requested chatbot. A chatbot-scoped key used with another chatbot's ID gets `Access denied to this chatbot`. A workspace key gets `Chatbot <id> was not found in this API key's workspace. It may have been deleted or moved to another workspace.` when the chatbot does not exist or belongs to another workspace.
- `429`: The workspace sent more than 600 API requests in the last minute. Wait the number of seconds given in the `Retry-After` header (and in `message`) before retrying.

---

[API](https://skmtc.dev/chat-data/apis/chat-data-api-schema-guide.md) · [All operations](https://skmtc.dev/chat-data/apis/chat-data-api-schema-guide/llms.txt) · [OpenAPI document](https://skmtc.dev/chat-data/apis/chat-data-api-schema-guide/revisions/72871007f7f0?raw)