Twitter API Wiki / HTTP Response Codes and Errors

<< Back to Twitter API Documentation

 

HTTP Status Codes

The Twitter API attempts to return appropriate HTTP status codes for every request. It is possible to surpress response codes for the REST API.

 

• 200 OK: Success!
• 304 Not Modified: There was no new data to return.
• 400 Bad Request: The request was invalid.  An accompanying error message will explain why. This is the status code will be returned during rate limiting.
• 401 Not Authorized: Authentication credentials were missing or incorrect.
• 403 Forbidden: The request is understood, but it has been refused.  An accompanying error message will explain why. This code is used when requests are being denied due to update limits.
• 404 Not Found: The URI requested is invalid or the resource requested, such as a user, does not exists.
• 406 Not Acceptable: Returned by the Search API when an invalid format is specified in the request.
• 500 Internal Server Error: Something is broken.  Please post to the group so the Twitter team can investigate.
• 502 Bad Gateway: Twitter is down or being upgraded.
• 503 Service Unavailable: The Twitter servers are up, but overloaded with requests. Try again later. The search and trend methods use this to indicate when you are being rate limited.

 

Error Messages

When the Twitter API returns error messages, it does so in your requested format. For example, an error from an XML method might look like this:

 

<?xml version="1.0" encoding="UTF-8"?>

<hash>

  <request>/direct_messages/destroy/456.xml</request>

  <error>No direct message with that ID found.</error>

</hash>

 

<< Back to Twitter API Documentation

via apiwiki.twitter.com

Posted via web from Filemakerdave's Blog