/ximalaya/users/sounds

POST /api/ximalaya/users/sounds

Price: 20 credits

List the sounds an anchor has published across all of their albums, newest first

How to use it

Sounds arrive newest first across every album the anchor runs at once, so a prolific anchor's oldest work sits far past what any single request reaches - narrow with the keyword or go through the album instead. The keyword matches episode titles only and an unmatched word returns nothing at all. Rows here carry no publication time, so date the episodes through the sound itself if that matters.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Anchor uid, or an anchor link of the form /zhubo/{id} (examples: "61885848", "https://www.ximalaya.com/zhubo/186005355"; minLength: 1)
• count integer required — Max number of results (min: 1; max: 3000)
• keyword string nullable — Keep only sounds whose title matches this text (examples: "蛊真人"; minLength: 1)

Response

• @type string (default: "XimalayaUserSound")
• id integer required
• url string nullable
• track_title string nullable
• image string nullable
• duration integer nullable
• album_id integer nullable
• album_title string nullable
• album_url string nullable
• anchor_id integer nullable
• anchor_name string nullable
• anchor_url string nullable
• play_count integer nullable
• is_paid 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 anchor exists with this uid. 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.