Skip to content
LiteScribe.ai
Integrations/
Automation

Transcription API and Zapier Automation

LiteScribe has a REST transcription API and a Zapier app. The API uses a scoped API key you create in Settings, starts transcription jobs from a media URL, and pushes signed webhooks when a transcript completes. The Zapier app is built on that same API and ships one trigger, one action, and three searches. It is currently available by invite rather than through the public Zapier directory, and the API itself is open to every plan today.

Get Started

What You Can Automate Today

LiteScribe exposes a REST transcription API with API-key authentication and outbound webhooks. The Zapier app is a thin layer over that same API, so anything the Zapier app does you can also do directly over HTTP. Two things carry the weight for automation: starting a transcription job, and being told the instant a transcript is ready.

  • Start a transcription job from any audio or video URL
  • Receive a signed webhook when a transcript finishes processing
  • Pull the full transcript text, summary, speakers, and topics from the payload
  • Search your transcripts, jobs, and AI chat threads by ID or title
  • Scope each API key and revoke it the moment you no longer need it

Zapier App Status: Available by Invite

Here is exactly where this stands. The LiteScribe Zapier app is built and running against production, but it is not yet listed in the public Zapier App Directory, so searching for LiteScribe inside the Zap editor will not find it. Access is granted through an invite link to the app. Contact support and we will send you one. The REST API below carries no such restriction and works today on every plan.

  • The Zapier app is live and running against the production API
  • It is not listed in the public Zapier App Directory yet
  • Access is by invite link, available from support on request
  • The REST API and webhooks are open to all plans right now
  • Zaps built through the invite link keep working once the app is listed

Trigger: Transcript Completed

The Zapier app ships a single trigger, and it is the one that matters. Transcript Completed is a REST hook, so Zapier subscribes once and LiteScribe pushes the event the instant transcription finishes. No polling, and no waiting around for Zapier to run its next scheduled check.

  • Fires as soon as a transcription is fully processed
  • Optional project filter so one Zap can watch a single workspace
  • Payload carries the full transcript text, not just an excerpt
  • Also includes the AI summary, action items, topics, and tags
  • Speaker labels, duration, language, and a link to the transcript

Action: Create Transcription Job

The Zapier app ships one action. Hand it a publicly reachable audio or video URL and LiteScribe queues the transcription, then returns the job and media IDs so later steps can track it. Pair it with a Google Drive, Dropbox, or RSS trigger to transcribe files the moment they land.

  • Takes any audio or video URL as its input
  • Set a title and a target language, or let language detection run
  • Toggle speaker detection and AI summary generation per job
  • File it into a specific project as it is created
  • Returns job ID, media ID, and status for downstream steps

Searches: Find Existing Records

Three search steps let a Zap look up something that already exists instead of creating a new record, which is what you want in the middle of a multi-step workflow.

  • Find Transcript, by transcript ID or title search
  • Find Transcription Job, by job ID or current status
  • Find Chat Thread, by thread ID or the transcript it belongs to

Using the REST API Directly

If you would rather not wait for the Zapier listing, or you are wiring this into your own backend, n8n, or Make, the API is straightforward. Create a key under Settings then Integrations and send it as an Authorization header. The base URL is https://litescribe.ai/api/v1 and keys carry an lsk_ prefix.

  • Authenticate with the header Authorization: Api-Key lsk_yourkey
  • POST /zapier/jobs/transcribe/url starts a job from a media URL
  • POST /zapier/subscribe registers a webhook for an event type
  • GET /zapier/transcripts/search and /zapier/transcripts/:id read transcripts
  • POST /zapier/ai/ask puts a question to the AI about your transcripts

Webhook Events and Signatures

The API can push four event types to any URL you register, which is more than the Zapier app currently surfaces as triggers. Every delivery is signed so you can prove it came from LiteScribe, and failed deliveries are retried on a background schedule instead of being dropped.

  • transcript.completed fires when transcription finishes
  • summary.ready fires when the AI summary and action items land
  • chat.completed fires when the AI answers a chat message
  • share.created fires when a share link is generated
  • Signed with HMAC-SHA256 in the X-LiteScribe-Signature header
  • X-LiteScribe-Timestamp lets you reject replayed deliveries

Workflows Worth Building

The pattern that pays off fastest is transcript-completed piped straight into wherever your team already reads things.

  • Post the AI summary to a Slack channel the moment a call ends
  • Create a Notion or Airtable row with the transcript and action items
  • Write the full transcript into a Google Doc for editing
  • Attach the summary to the matching deal or contact in your CRM
  • Watch a Drive folder and transcribe every file that lands in it
  • Email stakeholders a summary without anyone opening LiteScribe
FAQ

Frequently Asked Questions

Yes. LiteScribe has a REST transcription API with API-key authentication and signed outbound webhooks, and the Zapier app is built on top of it. Create a key under Settings then Integrations, send it as an Authorization header against https://litescribe.ai/api/v1, and start jobs or subscribe to webhooks from any tool that can make an HTTP request.

Not yet. The Zapier app is built and running against production, but it has not been published to the public Zapier App Directory, so searching for it inside the Zap editor will not return a result. Access is currently granted by invite link. Contact support and we will send you one. The REST API works today with no invite needed.

One trigger, Transcript Completed, a REST hook that fires the instant a transcription finishes and carries the full transcript, summary, action items, speakers, and topics. One action, Create Transcription Job, which starts a transcription from an audio or video URL. Three searches: Find Transcript, Find Transcription Job, and Find Chat Thread.

Open LiteScribe, go to Settings then Integrations, and create a key. It is shown once at creation, so copy it straight into your password manager or into Zapier. Keys start with lsk_, are stored hashed rather than in plain text, and you can revoke any key instantly from the same screen.

Every webhook carries an X-LiteScribe-Signature header in the form sha256=hex, plus an X-LiteScribe-Timestamp header. Recompute an HMAC-SHA256 over the timestamp, a dot, and the raw request body using your signing secret, then compare it against the signature. Reject anything with an old timestamp to shut down replay attempts.

Failed webhook deliveries are recorded and retried automatically on a background schedule rather than dropped, so a brief outage on your side does not cost you the event. Zapier handles this transparently when you use the Zapier app.

Yes. Nothing about the API is Zapier-specific. It is a plain REST API with header authentication, so n8n, Make, Pipedream, a cron job, or your own service can all drive it. Register a webhook URL through POST /zapier/subscribe and you get the same push events the Zapier app receives.

Yes. A transcription job started through the API or a Zap bills exactly like one started in the app, against the same monthly allowance. The free plan includes 120 minutes every month, so you can build and test a workflow end to end without paying anything.

Yes. Keys carry scopes covering reads and writes for transcripts, jobs, chats, and shares, plus webhook subscription management, and each endpoint checks the scope it needs. Issue a separate key per integration so you can revoke one without breaking the others.

Related Integrations

Google Drive

Import audio and video directly from Google Drive.

Dropbox

Sync your Dropbox files for automatic transcription.

Ready to Connect Zapier?

Start transcribing for free today. No credit card required.

Get Started FreeAll Integrations