/qqmusic/singers/search

POST /api/qqmusic/singers/search

Price: 20 credits

Browse the QQ Music artist directory by region, gender, genre and romanised initial

How to use it

This browses a curated directory by attribute; it takes no keyword, so it will not find a named artist. Every filter left unset means no restriction on that axis, and the four combine, so narrowing on several at once can legitimately return nothing. The mids it returns are the ones the singer endpoint takes.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of singers to return (min: 1; max: 8000)
• area string nullable — Keep only singers the catalogue files under this region (one of: "mainland_china", "hong_kong_taiwan", "western", "japan", "korea")
• gender string nullable — Keep only solo men, solo women or groups; leave unset for all three (one of: "male", "female", "group")
• genre string nullable — Keep only singers the catalogue files under this genre (one of: "pop", "rap", "chinese_style", "rock", "electronic", "folk", "rnb", "ethnic", "light_music", "jazz", "classical", "country", "blues")
• initial string nullable — Keep only singers whose romanised name starts with this letter; `other` covers names that romanise to a digit or symbol (one of: "a", "b", "c", "d", "e", "f", "g", "h", "i", "j", "k", "l", "m", "n", "o", "p", "q", "r", "s", "t", "u", "v", "w", "x", "y", "z", "other")

Response

• @type string (default: "QqmusicSearchSinger")
• mid string required
• id string nullable
• name string nullable
• translated_name string nullable
• pinyin 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 — The entity was not found, or a precondition failed 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.