Skip to main content
GET
curl

Authorizations

Authorization
string
header
required

An API key (sig_...), or a session token from the web app.

Path Parameters

agentId
string<uuid>
required

The agent's id.

Pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
Example:

"3f1c2d4e-5a6b-4c7d-8e9f-0a1b2c3d4e5f"

callId
string<uuid>
required

The call's id in SignalMD (not the platform's call id).

Response

The trace.

object
enum<string>
required
Available options:
trace
callId
string<uuid>
required

The call's id in SignalMD.

Pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
Example:

"3f1c2d4e-5a6b-4c7d-8e9f-0a1b2c3d4e5f"

providerCallId
string | null
required
version
integer | null
required
direction
string | null
required
status
string | null
required

The platform's call status.

startedAt
string<date-time> | null
required
Example:

"2026-10-02T14:03:07.120Z"

endedAt
string<date-time> | null
required
Example:

"2026-10-02T14:03:07.120Z"

durationMs
number | null
required
disconnectionReason
string | null
required
turns
object[]
required
toolCalls
object[]
required
path
object[]
required

The flow steps the call went through, in order. A step visited twice appears twice.

transitions
object[]
required

Each move between consecutive steps of path, by step id.

latency
object
required
measures
object
required

Measurements of the conversation. Counts, not findings: whether any of them is a problem is for the issues to say.

platform
object
required

What the platform recorded, never what it concluded: the platform's own summary, sentiment and success flag are not included. No link to the call's audio is given: the recording stays with the platform.