Poll the job
Poll GET /api/v1/transcriptions/{id} until status reads done or failed. The response carries the language, duration, word count, billed minutes, the full text, the summary, and a segments array of timed, speaker-labeled lines.
{
"id": "…",
"status": "done",
"language": "en",
"duration_seconds": 1771,
"word_count": 4120,
"billed_minutes": 30,
"text": "Full transcript…",
"summary": "…",
"segments": [
{ "start": 0.0, "end": 4.2, "speaker": "Speaker 1", "text": "Welcome back." }
]
}List recent jobs
GET /api/v1/transcriptions lists your transcriptions, which is the cheap way to find a job id you no longer have to hand – for example when reconciling what an automated run produced.
Skip the polling
If you are wiring this into a service, a webhook is the better shape than a polling loop: Pepys posts transcription.completed or transcription.failed to your endpoint and you fetch the full transcript only once, when there is actually something to fetch.