These pages contain the complete specification of how the App.net API works. We try to follow standard practices to make our API easy to use from one of our client libraries or from any normal HTTP client.
We use the OAuth 2.0 protocol to authenticate clients to the API. There are multiple ways to get a token to a user’s account. Please read our Authentication Overview to choose the right one for your app.
Our API responses are always JSON encoded. We use HTTP status codes to indicate success or failures.
From time to time, we’ll need to change the API. If we change the behavior of an endpoint or remove a field, we will provide a migration so clients can opt into the new behavior when their code is updated. Migrations are our way of versioning the App.net API. They allow your app the flexibility to control which version of the API it uses on a per request or global basis.
In order to ensure a high quality of service and prevent abuse, our API is rate limited. We use standard HTTP headers and status codes to rate limit requests. For more information (and to view the current rate limits), please see the Rate Limits documentation.
If there is an error, we return an HTTP status code and a JSON response describing it.