idstring
Spotify podcast show ID (alternative to url).
Spotify Podcast Episodes
https://api.sandbase.ai/v1/api/spotify/podcast-episodesList a Spotify podcast show's episodes with titles, durations, descriptions, and release dates by show URL or ID.
- Price
- From $0.0012USD / call
- Method
- POST
- Response
- JSON
- Parameters
- 0 required · 3 optional
Playground
Input
Spotify podcast show ID (alternative to url).
Spotify podcast show URL (e.g. https://open.spotify.com/show/4rOoJ6Egrf8K2IrywzwOMk).
Pagination cursor from a previous response for subsequent pages.
OutputReady
Your output will appear here
Complete the inputs, then click Run.
API README
Spotify Podcast Episodes API
List a Spotify podcast show's episodes with titles, durations, descriptions, and release dates by show URL or ID.
Request
curl -X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "spotify/podcast-episodes", "url": "https://open.spotify.com/show/4rOoJ6Egrf8K2IrywzwOMk"}'
The result is returned in outputs[0].data. Lookups that find nothing fail with a not-found error.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
cursor | string | No | Pagination cursor from a previous response for subsequent pages. |
id | string | No | Spotify podcast show ID (alternative to url). |
url | string | No | Spotify podcast show URL (e.g. https://open.spotify.com/show/4rOoJ6Egrf8K2IrywzwOMk). |
Pricing
Billed at the actual cost of each call, about $0.0012 per request. 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
Send your first request
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/podcast-episodes" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"url": "https://open.spotify.com/show/4rOoJ6Egrf8K2IrywzwOMk"
}
SANDBASE_JSON
)
printf '%s\n' "$result"2. Authentication
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.
3. Parameters
urlstring
Spotify podcast show URL (e.g. https://open.spotify.com/show/4rOoJ6Egrf8K2IrywzwOMk).
cursorstring
Pagination cursor from a previous response for subsequent pages.
4. Response
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
Related APIs
| API | Price | Response |
|---|---|---|
Spotify Podcast EpisodesThis API Spotify | From $0.0012 per call | JSON |
Spotify | From $0.0012 per call | JSON |
Spotify | From $0.0012 per call | JSON |
Spotify | From $0.0022 per call | JSON |
Spotify | From $0.0012 per call | JSON |
Spotify | From $0.0012 per call | JSON |
Questions
FAQ
How do I use the Spotify Podcast Episodes API?
Send a POST request to https://api.sandbase.ai/v1/api/spotify/podcast-episodes 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.
How much does the Spotify Podcast Episodes API cost?
From $0.0012 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
What parameters does the Spotify Podcast Episodes API accept?
No parameters are required. Optional: id (string), url (string) and cursor (string). The Parameters table and the Playground on this page list every field.
What does the Spotify Podcast Episodes API return?
A JSON response returned in the same HTTP request (synchronous).
Do I need a Spotify developer account or API key?
No. Spotify Podcast Episodes 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.