---
title: "Get the admin live chat link"
method: GET
path: "/get-admin-live-chat-link/{conversationId}"
tags: ["Conversation Operations"]
---

# Get the admin live chat link

`GET /get-admin-live-chat-link/{conversationId}`

## Request

- Base URL: `https://api.chat-data.com/api/v2`
- URL: `https://api.chat-data.com/api/v2/get-admin-live-chat-link/{conversationId}`
- Auth: HTTP bearer

Generate an admin live chat portal link for a specific conversation. This endpoint allows authorized users to access the admin interface for managing live chat conversations.

Requirements:
- Your plan must include live chat.
- Live chat must be enabled in the chatbot's settings.

Both `conversationId` (path parameter) and `chatbotId` (query parameter) are required.

## Path parameters

- `conversationId` string, required

## Query parameters

- `chatbotId` string, required

## Response `200`

Successful response.

- object
  - `status` 'success', required
  - `portalLink` string, required: The admin live chat portal link for the conversation.

## Other responses

- `400`: The `chatbotId` query parameter is missing, the plan does not include live chat, or live chat is not enabled for the chatbot.
- `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 chatbot given in the `chatbotId` query parameter: a chatbot-scoped key used with another chatbot's ID gets `Access denied to this chatbot`, and any key gets `Chatbot <id> was not found in this API key's workspace. It may have been deleted or moved to another workspace.` when that chatbot does not exist or belongs to another workspace.
- `404`: The chatbot has no conversation (stored or in an active live session) with this ID.
- `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.
- `500`: An unexpected error occurred while processing the request; `message` contains the error.

---

[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)