transcript_not_available

The episode was discovered in its podcast’s back catalogue and has not been transcribed.

HTTP status	409 Conflict
Error code	transcript_not_available

What happened

You asked for something transcription produces — the transcript, segments, speakers, entities, topics, ads, clips, or related episodes — of an episode whose transcript_status is requestable or queued. We found the episode in its podcast’s feed, so GET /v1/podcasts/episodes/{id} returns its metadata, but we have not transcribed it, so there is nothing to derive from.

An ID that matches no episode at all is still 404 not_found.

Example

{
  "type": "https://docs.particle.pro/errors/transcript_not_available",
  "title": "Conflict",
  "status": 409,
  "detail": "Episode 3kTMd9Z8vQ2xR7bL1nFpYa was discovered in its podcast's back catalogue and has not been transcribed, so it has no transcript yet.",
  "error_code": "transcript_not_available",
  "resolve": {
    "message": "Request its transcript with POST /v1/podcasts/transcription/requests and body {\"episode_id\": \"3kTMd9Z8vQ2xR7bL1nFpYa\"}, or skip episodes without a transcript by listing a podcast's episodes with transcript_status=transcribed.",
    "action": "request_transcription",
    "method": "POST",
    "endpoint": "/v1/podcasts/transcription/requests"
  }
}

How to fix

Request its transcript: POST /v1/podcasts/transcription/requests with its episode_id. Once it is transcribed, the call that answered 409 succeeds. A queued episode has already been requested; requesting it too gives you a request that follows the same transcription, billed only as a lookup.

Requesting needs an organization’s API key. A caller without one, such as one paying per request (x402) or an MCP client signed in with OAuth, gets a resolve that only suggests skipping the episode.

Or skip the episode. To list only episodes that have a transcript, pass transcript_status=transcribed.