Read one Warp conversation

Returns one of the caller’s threads with its transcript, bounded to the newest messages. Another user’s thread returns 404, the same as a missing one, so the response never confirms that it exists.

Registered only when Warp history storage is available.

Enterprise RBAC: requires WarpSession View.

GET /api/warp/conversations/{id}

Error

A valid request URL is required to generate request examples

200

{
  "id": "<string>",
  "title": "<string>",
  "message_count": 123,
  "total_tokens": 123,
  "total_cost": 123,
  "created_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z",
  "messages": [
    {
      "role": "user",
      "content": "<string>",
      "created_at": "2023-11-07T05:31:56Z",
      "tool_calls": [
        {
          "name": "<string>",
          "duration_ms": 123,
          "failed": true,
          "text_offset": 123
        }
      ],
      "error": "<string>",
      "finish_reason": "<string>",
      "total_tokens": 123,
      "cost": 123,
      "question": {
        "question": "<string>",
        "options": [
          {
            "label": "<string>",
            "hint": "<string>"
          }
        ],
        "allow_other": true,
        "kind": "<string>"
      }
    }
  ],
  "truncated": true
}

Authorizations

Authorization · string · header · required

Management API authentication for /api/* endpoints. Use the Authorization header with Bearer <token>, where <token> is one of:

• a Bifrost management API key,
• a dashboard session token issued by POST /api/session/login,
• base64 of <admin-username>:<admin-password> (legacy equivalent of BasicAuth).

Virtual keys (sk-bf-*) and the x-api-key header are not accepted on management APIs - the sole exception is GET /api/governance/virtual-keys/quota, which is virtual-key-only.

Authentication alone is not sufficient in Bifrost Enterprise: each operation page shows a Required Permissions table (Resource:Operation, for example Dashboard:View) above its Authorizations section, and the caller's RBAC role or management API key scopes must include what it lists, otherwise the request is rejected with 403 Forbidden.

A local admin — authenticated with the admin password, or any caller on a deployment with dashboard auth disabled — bypasses these checks and can call every management endpoint.

OSS setup lock. On Bifrost OSS, while dashboard auth is not active (no admin account, or auth disabled), every management endpoint except the public ones (/health, /api/version, /api/session/is-auth-enabled, /api/session/login, ...) requires the operator's setup token in the X-Bifrost-Setup-Token header, in place of Authorization. The token is set with setup_token in config.json or the BIFROST_SETUP_TOKEN environment variable. A missing header returns 401, a wrong token 403. The header stops working once dashboard auth is enabled. The dashboard instead trades the token once for an HttpOnly bifrost_setup_session cookie via POST /api/session/setup. See Required permissions for how permissions are derived and which endpoints are exempt.

Path Parameters

id · string · required

Response

200

application/json

The conversation and its transcript

One thread, without its messages.

id · string · required

title · string · required

The opening question, trimmed.

message_count · integer · required

total_tokens · integer · required

Tokens spent on the thread's answers so far.

total_cost · number · required

Cost of the thread's answers so far.

created_at · string<date-time> · required

updated_at · string<date-time> · required

messages · object[] · required

The newest messages, oldest first.

Show child attributes

truncated · boolean

True when older messages were cut to the transcript bound. message_count still reports the thread's real size.