/netease/tracks/lyrics

POST /api/netease/tracks/lyrics

Price: 1 credit

Get the lyrics of a NetEase Cloud Music track, with the translated, romanised and karaoke versions

How to use it

The text comes back in LRC form — one `[mm:ss.xxx]` timestamp per line — so strip the timestamps before showing it to a reader. A translation, a romanisation and a karaoke track are separate optional fields and most songs carry none of them, so treat their absence as normal. `is_instrumental` marks a song whose only lines are the writing credits.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• track string required — Track id, or a NetEase Cloud Music track page URL (examples: "186016", "https://music.163.com/song?id=186016"; minLength: 1)

Response

• @type string (default: "NeteaseLyrics")
• track_id string required
• url string nullable
• text string nullable
• translated_text string nullable
• romanised_text string nullable
• karaoke_text string nullable
• version integer nullable
• translated_version integer nullable
• romanised_version integer nullable
• karaoke_version integer nullable
• contributor object nullable
  • @type string (default: "NeteaseLyricsContributor")
  • id string required
  • name string nullable
  • url string nullable
  • updated_at integer nullable
• translator object nullable
  • @type string (default: "NeteaseLyricsContributor")
  • id string required
  • name string nullable
  • url string nullable
  • updated_at integer nullable
• is_instrumental boolean nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No track exists for the given id, or it carries no lyrics. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.