album_idstringrequired
Numeric album ID (e.g. 77855794). Obtainable from get_category_albums or search_albums results.
https://api.sandbase.ai/v1/api/ximalaya/album-tracksList tracks within an album with pagination. Returns track title, duration (seconds), play count, likes, comments count, pricing info, and order number. Paginates via page number.
Your output will appear here
Complete the inputs, then click Run.
List tracks within an album with pagination. Returns track title, duration (seconds), play count, likes, comments count, pricing info, and order number. Paginates via page number.
curl -X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "ximalaya/album-tracks", "album_id": "81519744"}'
The result is returned in outputs[0].data.
| Name | Type | Required | Description |
|---|---|---|---|
album_id | string | Yes | Numeric album ID (e.g. 77855794). Obtainable from get_category_albums or search_albums results. |
page | integer | No | Page number for pagination. |
page_size | integer | No | Number of tracks per page. |
sort_asc | string | No | Sort order. Accepted values: true (ascending by track order), false (descending). |
Flat $0.03 per call. Failed calls are not charged.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/ximalaya/album-tracks" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"page": 1,
"album_id": "81519744",
"sort_asc": "true",
"page_size": 5
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
album_idstringrequiredNumeric album ID (e.g. 77855794). Obtainable from get_category_albums or search_albums results.
pageintegerPage number for pagination.
Default: 1
sort_ascstringSort order. Accepted values: true (ascending by track order), false (descending).
Default: "true"
page_sizeintegerNumber of tracks per page.
Default: 30
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
Ximalaya Album TracksThis API Ximalaya | $0.03 per call | JSON |
Ximalaya | $0.03 per call | JSON |
Ximalaya | $0.03 per call | JSON |
Ximalaya | $0.03 per call | JSON |
Ximalaya | $0.03 per call | JSON |
Ximalaya | $0.03 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/ximalaya/album-tracks with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
$0.03 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: album_id (string). Optional: page (integer), sort_asc (string) and page_size (integer). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Ximalaya Album Tracks runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Ximalaya API access separately.