Skip to main content
GET
/
v1
/
recordings
/
{id}
Get Recording
curl --request GET \
  --url https://api.example.com/v1/recordings/{id}
{
  "id": "<string>",
  "toNumber": "<string>",
  "fromNumber": "<string>",
  "duration": 123,
  "status": "<string>",
  "direction": "<string>",
  "createdAt": "<string>",
  "transcript": {
    "text": "<string>",
    "wordCount": 123,
    "words": [
      {
        "word": "<string>",
        "start": 123,
        "end": 123,
        "speaker": "<string>"
      }
    ]
  }
}
Returns detailed information about a specific recording, including the full transcript with word-level timestamps.

Path Parameters

id
string
required
The recording ID

Request

curl -X GET "https://app.transcord.app/api/v1/recordings/clx1234567890" \
  -H "Authorization: Bearer tr_live_your_api_key"

Response

id
string
Unique recording identifier
toNumber
string
Destination phone number
fromNumber
string
Caller phone number
duration
number
Call duration in seconds
status
string
Recording status: completed, transcribing, processing, failed
direction
string
Call direction: outbound or inbound
createdAt
string
ISO 8601 timestamp
transcript
object
Full transcript data (only present when status is completed)
Response
{
  "id": "clx1234567890",
  "toNumber": "+14155551234",
  "fromNumber": "+14155555678",
  "duration": 342,
  "status": "completed",
  "direction": "outbound",
  "createdAt": "2026-01-15T10:30:00.000Z",
  "transcript": {
    "text": "Hello, this is John calling about the interview...",
    "wordCount": 847,
    "words": [
      {
        "word": "Hello,",
        "start": 0.5,
        "end": 0.9,
        "speaker": "you"
      },
      {
        "word": "this",
        "start": 1.0,
        "end": 1.2,
        "speaker": "you"
      }
    ]
  }
}

Processing Status

If the recording is still being processed, the transcript field will be absent and the status will indicate the current state:
{
  "id": "clx1234567890",
  "status": "transcribing",
  ...
}
Poll the endpoint until status becomes completed.

Errors

StatusDescription
401Invalid or missing API key
404Recording not found