/qqmusic/songs

POST /api/qqmusic/songs

Price: 1 credit

Get a QQ Music song with its singers, album, music videos and release details

How to use it

Song mid and numeric song id both resolve here, and so does a song page URL. Mids are type-scoped: an album or singer mid is rejected rather than silently resolved. Read comment_count before asking for comments, and videos for the music videos tied to this song.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• song string required — Song mid, numeric song id, or a QQ Music song page URL (examples: "0039MnYb0qxYhV", "97773", "https://y.qq.com/n/ryqq/songDetail/0039MnYb0qxYhV"; minLength: 1)

Response

• @type string (default: "QqmusicSong")
• mid string required
• id string nullable
• name string nullable
• subtitle string nullable
• url string nullable
• image string nullable
• singers array (default: [])
  • @type string (default: "QqmusicSongSinger")
  • mid string required
  • id string nullable
  • name string nullable
  • url string nullable
  • image string nullable
• album object nullable
  • @type string (default: "QqmusicSongAlbum")
  • mid string required
  • id string nullable
  • name string nullable
  • published_date string nullable
  • url string nullable
  • image string nullable
• duration_seconds integer nullable
• published_date string nullable
• disc_number integer nullable
• track_number integer nullable
• bpm integer nullable
• is_exclusive boolean nullable
• is_paid_play boolean nullable
• is_paid_download boolean nullable
• is_vip_only boolean nullable
• description string nullable
• language string nullable
• genre string nullable
• company string nullable
• wiki_url string nullable
• comment_count integer nullable
• videos array (default: [])
  • @type string (default: "QqmusicSongVideo")
  • vid string required
  • id string nullable
  • name string nullable
  • url string nullable
  • image string nullable
  • duration_seconds integer nullable
  • play_count integer nullable
  • singers array (default: [])
    • @type string (default: "QqmusicSongSinger")
    • mid string required
    • id string nullable
    • name string nullable
    • url string nullable
    • image string 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 song exists for the given id. 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.