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
| Platform | Path | Guide |
|---|---|---|
| YouTube | POST /api/youtube/transcript | YouTube → |
| TikTok | POST /api/tiktok/transcript | TikTok → |
POST /api/instagram/transcript | Instagram → | |
POST /api/facebook/transcript | Facebook → |
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:
| Platform | transcript type | Per-line timing | Video URLs included |
|---|---|---|---|
| YouTube | array of segment objects | yes (startMs, endMs, startTimeText) | no |
| TikTok | string (newline-joined) | no | yes (when available, in videoUrls) |
array of {text} objects (under transcripts, plural) | no | no | |
| string (newline-joined) | no | yes (when available, in videoUrls) |
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)