POST to https://api.transcriptmagic.com with {"url": "..."} in the body. Auth, path style, and the body field are identical across platforms — but the response shape differs by platform, because each upstream source emits different metadata. The per-endpoint pages below document the exact shape you can expect from each.
Base URL
Endpoints
The social-video endpoints above are synchronous — one request returns the transcript. Podcast transcription (Spotify, Apple Podcasts) is asynchronous: submit an episode, then poll
GET /api/podcast/jobs/{jobId}. It’s a Plus/Pro feature billed at 10 credits per audio-hour. See the Spotify and Apple Podcasts guides.Request
All endpoints accept the same body and headers. HeadersResponse
All endpoints return200 OK on success and always include a credits field with your remaining balance. Beyond that, the shape varies:
See the response schema page for the full per-platform field reference, or jump into a per-endpoint page for a real example payload.
Errors
All endpoints share the same error vocabulary — see errors for the full table. The most common ones:400— bad URL in the body, missingurl, or invalid JSON401— missing or invalid API key403— out of credits (error: "no_credits")404— upstream says the video is missing, private, or has no captions429— over the rate limit502— upstream platform HTTP error (retry with backoff)