Turn audio files into public URLs for transcription APIs
Use GetFileURL when a recording, voice note, podcast clip, or generated audio file needs a direct URL for a transcription, AI, or publishing API.
Audio APIs often fetch recordings by URL.
A workflow might receive audio from a form, call platform, app upload, or AI generator. The transcription API needs a URL it can fetch directly.
Call recordings
Host recordings long enough for transcription, QA, or CRM enrichment jobs.
Voice notes
Turn user-uploaded audio into a URL for support, ticketing, or summarization workflows.
Generated audio
Pass AI-generated audio through moderation, publishing, or storage steps.
Audio MIME type and expiry affect downstream processing.
Transcription and voice APIs can reject files when content type, codec, size, or availability does not match their input contract.
Content type
Use the right audio MIME type so the destination does not treat the file as generic binary data.
Codec and format
Make sure the destination accepts the file format before uploading large recordings.
Processing window
Set expiry long enough for queue delays and async transcription fetches.
Audio can be sensitive, so design a short lifecycle.
Recordings can contain personal or business information. Use expiry and delete controls around the workflow job.
Short retention
Use the shortest useful URL lifetime for transcription or summarization jobs.
Delete after fetch
Delete public access after the destination confirms it downloaded or processed the audio.
Avoid public archives
Use a podcast or media host when the goal is permanent distribution, not a workflow handoff.
Copy the same upload shape into code or workflow steps
Use the same endpoint from a shell, backend route, worker, or automation code step. Upload the file, set expiry, then map the returned URL.
cURL
upload examplecurl -X POST https://api.getfileurl.com/v1/files \
-H 'Authorization: Bearer $GETFILEURL_KEY' \
-F 'file=@voice-note.mp3' \
-F 'expires_in=24h'JavaScript
upload exampleconst form = new FormData();
form.append("file", file);
form.append("expires_in", "24h");
const res = await fetch("https://api.getfileurl.com/v1/files", {
method: "POST",
headers: { Authorization: `Bearer ${process.env.GETFILEURL_KEY}` },
body: form,
});
const { url, file_id } = await res.json();
return { url, file_id };Answers before the workflow breaks
Can I use the URL for transcription APIs?
Yes, when the transcription provider accepts public audio URLs and the file type, codec, size, and expiry window match its requirements.
Is this a podcast hosting product?
No. It is for direct audio file URL handoffs between workflow steps, not feeds, players, analytics, or public podcast distribution.
Should audio URLs expire?
Usually yes. Audio can contain sensitive information, so use short expiry and delete after processing when possible.