{"id":21657,"date":"2013-05-11T15:21:26","date_gmt":"2013-05-11T09:51:26","guid":{"rendered":"http:\/\/vskills.in\/certification\/tutorial\/?p=21657"},"modified":"2024-04-12T14:23:44","modified_gmt":"2024-04-12T08:53:44","slug":"http-response-codes","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/http-response-codes\/","title":{"rendered":"HTTP Response codes"},"content":{"rendered":"

Certify and Increase Opportunity.<\/span>
\nBe <\/span>
\nGovt. Certified Twitter Apps Developer
\n<\/span><\/a><\/p>\n

HTTP Response Codes and Errors<\/h1>\n

Upon executing a proxied Twitter API request, whether successful or not, the SuperTweet.net API returns the response status code and any error messages received from the Twitter API. This means that even if the SuperTweet.net proxy request succeeded, in the sense that the Twitter API was invoked, an error status code and corresponding error message may still be returned, as a result of an error on the Twitter side. A special header is provided in the response, set by the SuperTweet.net API proxy, as follows:<\/p>\n

X-TwitterAPI-Status: status-code<\/i><\/code><\/p>\n

If this header exists in the response, then the status code and error message represent those returned by the Twitter API. If this special header isnot<\/b> present in the response, then the status code and error message are those of the SuperTweet.net API service itself (not from the Twitter API).<\/p>\n

http status codes<\/h2>\n

The SuperTweet.net API returns the response status code received from the Twitter API, generally defined as.<\/p>\n