Integrations

Build Zipscribe into your own workflow

Zipscribe integrates through its REST API. Submit audio, track jobs, pull finished transcripts and translations, and monitor usage, all authenticated with your own API keys and billed against your monthly minutes.

The REST API

One API for transcription and translation

The Zipscribe API gives your code the same power as the app. Everything runs over straightforward HTTPS endpoints authenticated with a Bearer API key.

Submit for transcription

POST a media URL, including a YouTube link or a hosted audio or video file, and Zipscribe queues the job. The response returns a job id you can track. Transcription and translation run on the Zipscribe Engine.

List your jobs

Fetch the jobs tied to your API key with their status, progress, name, duration, and creation time, so your app always has an up-to-date view of what is processing and what is done.

Fetch a finished transcript

Retrieve a single job by id to get the full transcript once it is ready, along with timestamps, detected speakers, an optional summary, and generated YouTube titles, descriptions, and tags.

Check usage

Read your current plan, minutes used, minutes remaining, and monthly limit programmatically, so you can surface usage in your own dashboards or gate work before you hit a limit.

Manage API keys

Create and revoke API keys from your dashboard. Each key authenticates with a standard Bearer token and is scoped to your account. The secret is shown once at creation, so store it securely.

Usage-based billing

API usage draws from your monthly minute allowance, the same balance as the app. When minutes run out, requests return a clear response so your integration can handle it gracefully. Upgrade any time for higher limits.

How it works

From API key to finished transcript

A simple, poll-based flow that is easy to wire into any backend or script.

1

Create an API key

Sign in and open your Zipscribe dashboard. API access is available on the Pro plan and above. Generate a key, copy the secret once, and store it where your app can read it safely.

2

Submit and track a job

Send a media URL to the transcribe endpoint with your key as a Bearer token. You get back a job id right away, then poll the job endpoint to watch status and progress move toward done.

3

Pull the results

Once a job is complete, fetch it to read the transcript, timestamps, speakers, and SEO content. Export the text as TXT, SRT, or JSON and route it wherever your workflow needs it.

What it enables

What you can build

The API is the integration surface. Here is what programmatic access unlocks for your product and your team.

Transcription in your product

Add accurate transcription and translation to your own app, portal, or internal tool without building an audio pipeline.

Translation on demand

Send audio in one language and pull readable text, with support for translation across 99+ languages through the Zipscribe Engine.

Pull audio from sources like YouTube

Point the API at a YouTube link or a hosted media file. Zipscribe fetches the audio and does the work, no manual downloads required.

Automate your workflows

Kick off jobs from your own scripts and backends, then poll for completion to move finished transcripts into the next step automatically.

Clean, structured exports

Results come back ready to use as TXT, SRT, or JSON, so captions, transcripts, and metadata drop straight into your systems.

Scoped, revocable access

Every request is authenticated with an account-scoped API key you can revoke at any time from your dashboard.

Ready to start building?

Create an account, generate an API key from your dashboard, and start sending audio in minutes. API access is available on the Pro plan and above.