Transcribr API

Send a URL. Get a transcript and a plan.

The Transcribr public API lets you submit audio programmatically and retrieve transcripts, summaries, and extracted action plans. Authenticate with an API key you generate from Settings. Full interactive reference available at api.transcribr.co/docs.

Quickstart

1. 1. Create an API key. Sign in to Settings → API Keys, click "Create Key", and copy the returned value. It's shown only once.
2. 2. Submit an audio URL. POST to /api/v1/ingest with a publicly reachable audio_url. Transcribr queues the job and returns a job_id.
3. 3. Poll for status. GET /api/v1/ingest/{job_id} until status is completed; the outputs field then contains your transcript and downstream artifacts.

Examples

Submit a recording

curl -X POST https://api.transcribr.co/api/v1/ingest \
  -H "X-API-Key: $TRANSCRIBR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "audio_url": "https://example.com/my-meeting.mp3",
    "filename": "q1-kickoff.mp3"
  }'

Check job status

curl https://api.transcribr.co/api/v1/ingest/$JOB_ID \
  -H "X-API-Key: $TRANSCRIBR_API_KEY"

Upload a large file via S3 presign

curl -X POST https://api.transcribr.co/api/v1/ingest/presign \
  -H "X-API-Key: $TRANSCRIBR_API_KEY"
# → { upload_url, audio_url }
# PUT your bytes to upload_url, then POST /api/v1/ingest with the returned audio_url.

Authentication

All public endpoints accept a single header: X-API-Key: trk_…. Keys have two scopes: ingest (submit audio, request presigned uploads) and read (poll job status, list webhook logs). You can create keys scoped to yourself or to an organization.

Webhook activity log

Every ingest call is recorded and surfaced in Settings → API Keys → "Recent webhook activity". Use it to debug 4xx responses, confirm successful job creation, and spot stalled runs.

Operational

• Supported audio extensions: mp3, wav, m4a, mp4, webm, ogg, opus, flac, aac, mov, aiff, wma.
• audio_url must be http:// or https://; other schemes return 422.
• Invalid requests return 422 with a user-readable detail field — map them through to your end-user UI.
• Uptime and incident history: status.transcribr.co.