REST API
What is REST API?
Libraryminds REST API is a built-in capability. The REST API feature gives products and automations programmatic access to Libraryminds. Submit asynchronous transcription jobs, check status, retrieve timestamped transcripts, search a library, and connect signed webhooks. The developer documentation is the canonical source for v1 implementation details.
Read the Libraryminds API documentation — Start with the v1 quickstart, then check authentication, scopes, endpoints, rate limits, errors, and webhooks.
- ✓ Submit YouTube URLs, public HTTPS media URLs, or file uploads
- ✓ Retrieve transcript segments as JSON or download text, SRT, and VTT
- ✓ Use endpoint-specific scopes on lm_live_ Bearer keys
- ✓ Default limit of 60 requests per minute per key
- ✓ REST API access is available on every plan; minutes and feature gates still apply
Available on the Free plan — no credit card required.
Use Cases
Add transcription to a SaaS product
A product team integrates the Libraryminds REST API to add AI transcription to their video hosting platform — users get searchable transcripts without the team building AI infrastructure.
Automate meeting transcript processing
A company's meeting bot submits recordings to the Libraryminds API after each call — receiving structured JSON with action items and summaries for automatic CRM logging.
Power a content intelligence pipeline
A media analytics firm uses the API to transcribe and index thousands of hours of broadcast content — building a searchable intelligence layer on top of their media archive.
Frequently Asked Questions
Which plan includes REST API access?
The REST API is available on all plans including Free. Usage is billed from your plan's monthly minute credits.
What authentication method does the API use?
The API uses scoped Bearer keys beginning with lm_live_. Keep the key server-side and send it in the Authorization header of each request.
Is there a rate limit?
The default limit is 60 requests per minute per API key. AI and chat endpoints also have operation-specific limits documented on the developer page.
Is there an OpenAPI / Swagger spec?
Yes. Verified v1 endpoints, scopes, examples, plan gates, and the OpenAPI 3.1 specification are linked from the developer documentation.
← Developer & Integration features · All features