Bubble transcription integration

For founders shipping a product with transcription inside it before writing a backend. The job: call the API from a workflow and store the transcript against a thing.

Wiring it up

1 · Trigger

Any of these start the run:

• Button workflow
• backend workflow on file upload

2 · Submit from API Connector

# submit — returns immediately, does not block
curl -X POST https://whipscribe.com/api/v1/transcribe/url \
  -H "X-API-Key: $KEY" \
  -H "Idempotency-Key: bubble-$FILE_ID" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com/recording.mp4",
       "diarize":true,
       "word_timestamps":true}'

→ 202 {"job_id":"a1b2…","status":"queued"}

# then poll — a self-serve (Pro) key collects by polling
curl "https://whipscribe.com/api/v1/jobs/$JOB" -H "X-API-Key: $KEY"
→ {"status":"processing"} … {"status":"done"}

3 · Collect

Submit, store the job id, and poll only the rows still queued.

# one job, every format — never re-submit per format
curl "https://whipscribe.com/api/v1/jobs/$JOB/result?format=txt" -H "X-API-Key: $KEY"
curl "https://whipscribe.com/api/v1/jobs/$JOB/result?format=srt" -H "X-API-Key: $KEY"
curl "https://whipscribe.com/api/v1/jobs/$JOB/result?format=vtt" -H "X-API-Key: $KEY"

What your key can actually do

What it costs to run

$8 per 1,000 minutes — about $0.48 an audio hour — and credits never expire.

Why run it here

Recipes that use Bubble