Skip to main content
GET
Get session details
Retrieve full details of a specific session by its ID.

Endpoint

Authentication

All requests require an API key passed in the x-api-key header.
Contact your workspace admin if you don’t have an API key.

Path Parameters

Response

Success (200)

Response Fields

duration, retryAttemptNo, and recordingUrl are only included for call sessions (SIP trunk channels). For chat, email, WhatsApp, and other non-call sessions, these fields are omitted entirely.

Transcript Entry Types

The transcript array contains entries in chronological order. Each entry has a type field that determines its structure.

1. Message (type: "message")

A text or media message from the user, agent, or background agent.

2. Function Call (type: "function_call")

The agent invoked a tool/function.

3. Function Call Output (type: "function_call_output")

The result returned by a tool execution.

4. Thinking (type: "thinking")

The agent’s internal reasoning for a turn.

5. Summary (type: "summary")

A generated summary of the conversation up to a certain point.

Content Item Types

Each message entry’s content array contains one or more items. The type field determines the structure.

Text

Image

Video

Audio

File

Button (Quick Reply)

Media URLs (image, video, audio, file) are signed and expire after a limited time. Download or cache them promptly.

Session Statuses


Errors

All errors follow the same response format:

401 — Unauthorized

Missing API key:
Invalid API key:

404 — Session Not Found

The session ID does not exist in the workspace associated with your API key.

422 — Validation Error

The sessionId path parameter is missing or empty.

500 — Internal Server Error


Code Examples

cURL

JavaScript

Python

Node.js (axios)

Authorizations

x-api-key
string
header
required

Authentication header containing API key from SubVerse dashboard.

Path Parameters

sessionId
string
required

The unique identifier of the session.

Minimum string length: 1
Example:

"sess_01H8XK3Q9V1YJZ5T7N2A8B9C0D"

Response

Session details found

responseCode
integer
required

HTTP status code indicating the result of the request.

Example:

200

message
string
required

Human-readable message describing the result of the request.

Example:

"Session details found"

data
object
required