API
GET /transcript/raw
Same data as /transcript, returned as a single plain-text blob.
When you don't need the structured segments — just the raw words for an LLM prompt or a download — use the raw endpoint.
GET https://api.repackage.app/transcript/rawQuery parameters
Same as GET /transcript — pass either id or url.
Example
curl "https://api.repackage.app/transcript/raw?id=dQw4w9WgXcQ" \
-H "Authorization: Bearer rpk_your_key_here"Response
200 OK, Content-Type: text/plain:
Video: Rick Astley - Never Gonna Give You Up
Channel: Rick Astley
Transcript:
We're no strangers to love You know the rules and so do I ...When to use this vs /transcript
- Use
/transcript/rawwhen you're piping the text straight into a prompt or saving it to disk. - Use
/transcriptwhen you need timestamps, multiple language tracks, or video metadata.
Both endpoints share quota and the same 24-hour cache, so calling either one warms the cache for the other.
Errors
Errors come back as text/plain (not JSON) with a status code. The body is the human-readable message; for structured handling, prefer /transcript.