urlstringrequired
Spotify track, album, or artist URL to fetch stream counts for (e.g. https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp).
https://api.sandbase.ai/v1/api/spotify/play-countFetch stream counts and stats for a Spotify track, album, or artist URL.
Your output will appear here
Complete the inputs, then click Run.
Fetch stream counts and stats for a Spotify track, album, or artist URL.
curl -X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "spotify/play-count", "url": "https://open.spotify.com/track/4cOdK2wGLETKBW3PvgPWqT"}'
The result is returned in outputs[0].data. Lookups that find nothing fail with a not-found error.
| Name | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Spotify track, album, or artist URL to fetch stream counts for (e.g. https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp). |
Billed at the actual cost of each call: about $0.0022 per result returned, up to $0.0022 per request (about $0.0022 for the request above). A call can cost more when the first data source fails and another one answers. Failed calls and lookups that find nothing 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/spotify/play-count" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"url": "https://open.spotify.com/track/4cOdK2wGLETKBW3PvgPWqT"
}
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.
urlstringrequiredSpotify track, album, or artist URL to fetch stream counts for (e.g. https://open.spotify.com/track/3n3Ppam7vgaVa1iaRUc9Lp).
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 |
|---|---|---|
Spotify Play CountThis API Spotify | From $0.0022 per call | JSON |
Spotify | From $0.0012 per call | JSON |
Spotify | From $0.0012 per call | JSON |
Spotify | From $0.0012 per call | JSON |
Spotify | From $0.0012 per call | JSON |
Spotify | From $0.0012 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/spotify/play-count 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.
From $0.0022 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: url (string). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Spotify Play Count 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 Spotify API access separately.