/qqmusic/singers

POST /api/qqmusic/singers

Price: 10 credits

Get a QQ Music singer with their biography, most-played songs, discography, music videos, band members and similar artists

How to use it

Only the singer mid resolves here, or a singer page URL containing it - the numeric singer id that appears inside other responses is rejected by the catalogue, so pass the mid. The lists are the head of each catalogue, not the whole of it; `song_count`, `album_count` and `video_count` report how much the artist actually has. A null count alongside an empty list is not distinguishable from the artist genuinely having none - treat it as inconclusive rather than as confirmation.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• singer string required — Singer mid, or a QQ Music singer page URL (examples: "0025NhlN2yWrP4", "https://y.qq.com/n/ryqq/singer/0025NhlN2yWrP4"; minLength: 1)

Response

• @type string (default: "QqmusicSinger")
• mid string required
• id string nullable
• name string required
• translated_name string nullable
• url string nullable
• image string nullable
• images array (default: [])
• description string nullable
• birth_date string nullable
• wiki_url string nullable
• members array (default: [])
  • @type string (default: "QqmusicSingerMember")
  • mid string required
  • id string nullable
  • name string nullable
  • translated_name string nullable
  • url string nullable
  • image string nullable
• song_count integer nullable
• album_count integer nullable
• video_count integer nullable
• top_songs array (default: [])
  • @type string (default: "QqmusicTrack")
  • 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
• albums array (default: [])
  • @type string (default: "QqmusicSingerAlbum")
  • mid string required
  • id string nullable
  • name string nullable
  • translated_name string nullable
  • album_type string nullable
  • published_date string nullable
  • track_count integer nullable
  • url string nullable
  • image string 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
• similar_singers array (default: [])
  • @type string (default: "QqmusicSimilarSinger")
  • 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 singer exists for the given mid. 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.