Partner · GET

Track play counts (batch)

GET /partner/tracks/count

With a key: 1,000 requests / month free on RapidAPI, 5 requests a second on every plan; from $9 for 20K requests direct, valid 30 days. Per-request cost at four volumes.

About

Lifetime play counts for up to 50 tracks in one call. Entries come back in request order with `status` `ok`, `not_found` or `error`; ids without a play count are also listed in `missing`. Each id is cached for 1 hour.

Parameters 2

ids Required
In
query
Default
—
Description
Comma-separated track IDs (1-50).
cache Optional
In
query
Default
—
Description
Set to `false` to skip the cached copy and fetch fresh data (the cache is updated with the result). A URL is refreshed at most once every 10 seconds.

Request

Sent to https://spotify-proxy.checkleaked.cc/spotify-data with a direct-portal key in the x-rapidapi-key header, using the same example values the Run button sends.

Using a RapidAPI key? Delete the provider line in the JavaScript tab: the SDK then sends your key to RapidAPI with the host header it needs. The code snippets RapidAPI generates on its spotify81 listing fill in your key and host too.

Sample response

Live only

This endpoint has no recorded sample. Press Run to fetch a real response.

Errors

400
“ids” is required — a request that omits it, or sends a value of the wrong type, is rejected before it reaches Spotify.
404
No Spotify item exists for the “ids” that was sent. Spotify ids are 22 characters of base62, so a share link has to be reduced to the id in it first.
401 / 403
The key is missing or not valid (code MISSING_API_KEY or INVALID_API_KEY). RapidAPI and the direct portal both read it from x-rapidapi-key; RapidAPI also needs x-rapidapi-host, which the SDK adds. On Apify the actor supplies it.
429
Rate limited. The demo on this site allows 100 requests per 15 minutes and 500 per day per visitor, inside a budget shared by every visitor. With a key it is 5 requests per second on every RapidAPI plan and 10 per second included with every direct key.
5xx
Temporary: wait for Retry-After, then retry two or three times at most. A 503's code names the cause — UPSTREAM_UNAVAILABLE, UPSTREAM_THROTTLED or LOAD_SHED. A timeout (UPSTREAM_TIMEOUT, or a 504) has already used the request's whole time budget, so retry it once at most. Retry a 500 with backoff.

Related endpoints

The other 6 operations in the Partner group.