Lyrics, in sync · An API for developers

Lyrics. Timing.
One request.

Bring song lyrics to your player.
Four sources, one JSON format, and synchronization whenever it is available.

LYRICS / SYNCED
The city falls asleep outside
We find a rhythm in the quiet
Every sound in its place
Every line has its own time
plain_lyrics + lines + wordsFICTIONAL EXAMPLE

One fallback chain.
First lyrics found.

  1. 01 Octave
  2. 02 Musixmatch
  3. 03 Genius
  4. 04 lyrics.lol
01 / QUICK START

Just name the song.

Send a track title and artist.
The adapter finds the metadata Octave needs.

POST/v1/lyrics
Content-Type: application/json
curl "$API_BASE_URL/v1/lyrics" \
  -H 'Content-Type: application/json' \
  -d '{"title":"Operation Cyclone","artist":"Ghais Guevara"}'
Response / JSON
Example response
{
  "provider": "octave",
  "plain_lyrics": "Every sound in its place",
  "synced_lyrics": "[00:12.40]Every sound in its place",
  "lines": [
    {
      "start": 12.4,
      "end": null,
      "text": "Every sound in its place"
    }
  ]
}

The panel shows a shortened response with fictional lyrics.
The button sends a real request to this service’s API.

In cURL and Python, API_BASE_URL is your deployment’s base address. JavaScript uses a relative path on the same origin.

02 / ONE RESPONSE FORMAT

From plain text
to every word.

Use the detail your source provides. Every source returns one consistent format, so your app needs only one integration.

Explore the response schema
  1. 01

    Plain lyrics

    Song lyrics without timestamps. The basic format for displaying and saving text.

    plain_lyrics
  2. 02

    Line synchronization

    The original LRC plus an array of lines timed in seconds. Ready for highlighting during playback.

    synced_lyrics / lines
  3. 03

    Word timestamps

    Start and end timestamps for individual words, when the source provides this level of detail.

    words

Find every detail in the docs.

Parameters, errors, response examples, and the Python library.

Open documentation