Things to know / remember
The API is REST-based. All requests follow a standard format, see the api introduction for an overview of how to perform these requests.
All parts of a URL in bold are parameters that should be replaced before making calls!
/account/... urls will act on the user corresponding to the OAuth access token provided. They will return an unauthorized response if OAuth authentication hasn't been performed.
The different API endpoints are broken up by section :
Some users may be blocked from messaging or following others.
If you GET the details of an individual user, there is a
messaging_enabled flag indicating whether that user can be messaged, and likewise for the
Each message in the inbox contains a
user[messaging_enabled] flag showing if that message can be replied to.
Only JPEG and PNG image formats are tested and known to work at the point.
We will attempt to transcode any audio file that you throw at us. We explicitly support FLAC, MP3, and AIFF/WAV.
Files should be sent using HTTP multipart encoding. You must include a 'filename' parameter in the Content-Disposition multipart header, to ensure that our webserver processes it as a file. If you're authenticating via OAuth 1, be sure to use the Body Hash extension.