/ximalaya/albums/sounds

POST /api/ximalaya/albums/sounds

Price: 20 credits

List the sounds (episodes) of a Ximalaya album, newest first

How to use it

Episodes come back newest first and there is no way to start from the oldest, so reaching the first episode of a long-running show means asking for the whole run. Album, sound and anchor ids share one numeric range, so pass the /album/{id} link when you have it rather than a bare number.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• album string required — Album id, or an album link of the form /album/{id} (examples: "81519744", "https://www.ximalaya.com/album/40121646"; minLength: 1)
• count integer required — Max number of results (min: 1; max: 5000)

Response

• @type string (default: "XimalayaAlbumSound")
• id integer required
• url string required
• track_title string nullable
• description string nullable
• image string nullable
• duration integer nullable
• sample_duration integer nullable
• album_id integer nullable
• album_title string nullable
• album_url string nullable
• anchor_id integer nullable
• anchor_url string nullable
• category_id integer nullable
• category_title string nullable
• play_count integer nullable
• price number nullable
• discounted_price number nullable
• created_at integer nullable
• updated_at integer nullable
• is_paid boolean nullable
• is_offline boolean nullable
• is_copyright_held 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 album exists with this id, or it publishes no sounds. 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.