---
title: "Check access to a conversation's live stream"
description: "Answers 204 when the caller may read the conversation. The website's Worker asks this before it opens the WebSocket at the history page's live_url, with the caller's own credentials; clients connect…"
canonical: "https://www.cool.computer/docs/api-reference/operator/check-access-to-a-conversations-live-stream"
---
# Check access to a conversation's live stream

> Answers 204 when the caller may read the conversation. The website's Worker asks this before it opens the WebSocket at the history page's live_url, with the caller's own credentials; clients connect…

```http
GET https://api.cool.computer/api/operator/conversations/{id}/live-access
```

Answers 204 when the caller may read the conversation. The website's Worker asks this before it opens the WebSocket at the history page's live_url, with the caller's own credentials; clients connect to live_url and never call this themselves.

## Authorization

- A Cool Computers API key, user access token, or claimed agent access token in the Authorization header. Follow https://www.cool.computer/auth.md for agent registration and https://www.cool.computer/authentication.md for direct user credentials.

## Parameters

- `id` (path, string, at least 1 characters, required): Operator conversation identifier.

## Responses

- `204`: The caller may read the conversation's live stream.
- `401`: Unauthorized.
- `404`: Not Found.
- `429`: Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit.
- `500`: Internal Server Error.
- `default`: A machine-readable API error with a stable code and recovery instruction.

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl "https://api.cool.computer/api/operator/conversations/$PARAM_ID/live-access" \
  -H "authorization: Bearer $TOKEN"
```
