Audio Bubble API v2.2
This is the documentation for the v2.2 Audio Bubble API (with both authentication and write support). If you have additional questions, or believe you have encountered a bug, don't hesitate to post a question on Audio Apps.
If your application is in a runnable state (even a beta one), Audio Apps is also the place to list it.
General
Applications should be registered on Audio Apps to get a request key. Request keys grant more requests per day, and are necessary for using access_tokens created via authentication.
All API responses are JSON, we do support JSONP with the callback query parameter. Every response in the API is returned in a common "wrapper" object, for easier and more consistent parsing.
Additionally, all API responses are compressed. The Content-Encoding header is always set, but some proxies will strip this out. The proper way to decode API responses can be found here.
API usage is subject to a number of throttles. In general, applications should strive to make as few requests as possible to satisfy their function.
API responses are heavily cached. Polling for changes should be done sparingly in any case, and polling at a rate faster than once a minute (for semantically identical requests) is considered abusive.
Developers can trim API responses down to just the fields they are interested in using custom filters. Many types have fields that are not normally returned (question bodies, for example) that can likewise be requested via a custom filter.
