API: Process Episode
Submit an episode for processing (transcription and AI analysis). Pro users consume AI processing credits. For Enterprise users, public-episode processing is included subject to fair use limits, while private imports and uploaded audio use Enterprise usage-based billing.
Endpoint
Path Parameters
seq: Episode sequence number (found in search results or Podwise URL).
Response
type Response = {
success: true,
result: {
// One of: "waiting", "processing", "done"
status: string,
// 100 when status is "done", null otherwise
progress: number | null,
},
}| Status | Description |
|---|---|
waiting | Episode is queued for processing. |
processing | Episode is currently being processed. |
done | Episode has already been processed. progress will be 100. |
Enterprise Webhook
Enterprise processing through Open API triggers webhook callbacks. The configured webhook receives OPEN_API_TRANSCRIBE_DONE or OPEN_API_TRANSCRIBE_ERROR when processing finishes.
A request that creates a task, restarts a failed task, or joins a task that is already waiting or processing registers a webhook notification with the episode seq. Delivery uses the webhook URL and active access token selected in the Enterprise Console.
If this endpoint immediately returns done, the episode was already processed and no webhook is sent. Repeated requests from the same Enterprise user during one processing cycle are coalesced into one notification.
See Webhook Notifications for payload definitions and delivery behavior.