Skip to main content
The lyrcs.ai API is currently available to music distributors, streaming platforms, rights management companies, and karaoke providers.

​
How to request access

Email support@lyrcs.ai with the following information:

Company name

Your organisation’s full legal name and any relevant brand names.

Use case

What you’re building — e.g. “deliver time-synced lyrics to DSPs for Indian language catalog” or “lyric display feature for streaming app”.

Expected monthly volume

Estimated number of tracks per month. This helps us provision the right rate limits for your account.

Languages

Which languages you primarily work with. Indian language catalogs receive enhanced processing.
We’ll respond within 2 business days with your API key and webhook secret.

​
What you’ll receive

  • An API key in the format lyrcs_live_... — used as the Bearer token in the Authorization header
  • A webhook secret — used to verify HMAC-SHA256 signatures on webhook deliveries
Both are scoped to your organisation. All jobs, usage, and webhooks are isolated to your org.
Keep your API key and webhook secret secure. Do not commit them to source control or expose them in client-side code. If you believe a key has been compromised, contact support@lyrcs.ai immediately.

​
Default rate limits

Submissions and reads are metered separately, so polling for a job’s status never consumes the budget you use to submit songs. Submissions — POST /transcribe, POST /batch, and POST /jobs/{id}/align. A batch counts as one submission per job it contains. POST /jobs/{id}/align is metered here rather than as a read because it runs the aligner, which is real per-call cost. Approving a held job (POST /jobs/{id}/approve) is not a submission — the job was charged when you created it. Reads — everything else: status checks, downloads, usage. Limits apply per organisation, not per API key — issuing additional keys does not increase them.
Prefer webhooks over polling where you can. The read budget is generous enough that polling will not normally reach it, but a webhook tells you the moment a job is done rather than up to a poll interval later.
If your catalog volume requires higher limits, mention it in your access request email.

​
Next steps after receiving your key

Quickstart

Submit your first job and download an LRC file in minutes.

Authentication

Learn how API keys work and how to use them securely.