Skip to content


Folders and files

Last commit message
Last commit date

Latest commit



21 Commits

Repository files navigation

Buzzsprout API

This is version one of the Buzzsprout API. This API has been designed around RESTful concepts with JSON for serialization.


All requests are SSL only and the API URL is where 9999 is the podcast identifier. If we change the API in backward-incompatible ways, we'll add the version marker and maintain stable support for old URLs.


Buzzsprout uses a simple token-based HTTP Authentication scheme. For clients to authenticate, the method "Token" and the token key should be included in the Authorization HTTP header. The key should be prefixed by the string literal "token=" with no whitespace. For example:

Authorization: Token token=ApV99yzvwApV99yzvwApV99yzvwApV99yzvw

Additionaly you can pass the api token as a paramater in the URL


To retrieve your token check out the my account section in your Buzzsprout admin at

Body Format

All data is serialized with JSON and UTF-8 encoded. This means that you have to send Content-Type: application/json; charset=utf-8 when you're POSTing or PUTing data into Buzzsprout. All API URLs end in .json to indicate that they accept and return JSON.

You'll receive a 415 Unsupported Media Type response code if you attempt to use a different URL suffix or leave out the Content-Type header.

Sample GET

To make a request for all the Episodes on your account, you'd append the episodes index path to the base url to form something like In cURL, that looks like:

curl -H "Authorization: Token token=ApV99yzvwApV99yzvwApV99yzvwApV99yzvw" \

Sample POST

To create something, it's the same deal except you also have to include the Content-Type header and the JSON data:

curl -H "Authorization: Token token=ApV99yzvwApV99yzvwApV99yzvwApV99yzvw" \
     -H 'Content-Type: application/json' \
     -d '{ "title": "My new episode!" }' \

Use HTTP caching

You must make use of the HTTP freshness headers to lessen the load on our servers (and increase the speed of your application!). Most requests we return will include an ETag or Last-Modified header. When you first request a resource, store this value, and then submit them back to us on subsequent requests as If-None-Match and If-Modified-Since. If the resource hasn't changed, you'll see a 304 Not Modified response, which saves you the time and bandwidth of sending something you already have.

Handling errors

If Buzzsprout is having trouble, you might see a 5xx error. 500 means that the app is entirely down, but you might also see 502 Bad Gateway, 503 Service Unavailable, or 504 Gateway Timeout. It's your responsibility in all of these cases to retry your request later.


Thank you for checking out Buzzsprout's API and please don't hesitate to reach out and let us know how you are using the API. Feel free to use GitHub issues to post any issues or feature requests.

Please tell us how we can make the API better. If you have a specific feature request or if you found a bug, please use GitHub issues. Fork these docs and send a pull request with improvements.

To talk with us and other developers about the API, post a question on StackOverflow tagged Buzzsprout or check out our support section.


The official documentation for the Buzzsprout API (






No releases published


No packages published

Contributors 4