Protocol Error 400 Twitter
Contents |
DocumentationBest PracticesAPI OverviewUpcoming changes to TweetsObject: UsersObject: TweetsObject: EntitiesObject: Entities in ObjectsObject: PlacesTwitter IDsConnecting to Twitter API using TLSUsing cursors to navigate collectionsError Codes & ResponsesTwitter LibrariesAPI StatusPlaybooksEventsCase StudiesManage My AppsTerms of UseError Codes & ResponsesHTTP Status CodesThe Twitter API attempts to return appropriate HTTP status codes for every request.CodeTextDescription200OKSuccess!304Not twitter error something is technically wrong ModifiedThere was no new data to return.400Bad RequestThe request was invalid or twitter internal server error when tweeting cannot be otherwise served. An accompanying error message will explain further. In API v1.1, requests without authentication are error codes http considered invalid and will yield this response.401UnauthorizedAuthentication credentials were missing or incorrect.Also returned in other circumstances, for example all calls to API v1 endpoints now return 401 (use API v1.1 internal server error twitter photo upload instead).403ForbiddenThe request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why. This code is used when requests are being denied due to update limits. Other reasons for this status being returned are listed alongside the response codes in the table below.404Not FoundThe URI requested is invalid or the resource requested, such
Rest Api Error Codes Best Practices
as a user, does not exists. Also returned when the requested format is not supported by the requested method.406Not AcceptableReturned by the Search API when an invalid format is specified in the request.410GoneThis resource is gone. Used to indicate that an API endpoint has been turned off. For example: "The Twitter REST API v1 will soon stop functioning. Please migrate to API v1.1."420Enhance Your CalmReturned by the version 1 Search and Trends APIs when you are being rate limited.422Unprocessable EntityReturned when an image uploaded to POST account / update_profile_banner is unable to be processed.429Too Many RequestsReturned in API v1.1 when a request cannot be served due to the application's rate limit having been exhausted for the resource. See Rate Limiting in API v1.1.500Internal Server ErrorSomething is broken. Please post to the developer forums so the Twitter team can investigate.502Bad GatewayTwitter is down or being upgraded.503Service UnavailableThe Twitter servers are up, but overloaded with requests. Try again later.504Gateway timeoutThe Twitter servers are up, but the request couldn't be serviced due to some failure within our stack. Try again later.Error MessagesWhen the
e.g. - https://ads-api.twitter.com/0/stats/accounts/18ce53ur22q/reach/campaigns?start_time=2016-01-06T00:00:00Z&end_time=2016-01-06T23:59:59Z&campaign_ids=3x9tp Returns - {"The remote server returned an error: (400) Bad Request."} ... and ... Status = ProtocolError
Message Error Text
Anyone seen anything like this before? Any tips greatly appreciated. internal server error twitter direct message majoritasdev 2016-02-17 12:18:35 UTC #2 Hi @niki_wiles! Maybe start_time and end_time must align to midnight facebook api error codes in the account's timezone?.. Take a look at https://dev.twitter.com/ads/basics/timezones the second paragraph under the title "Specifying Datetime Values With Timezone" - this is about https://dev.twitter.com/overview/api/response-codes the endpoints that use the granularity parameter, but maybe this applies to your endpoint as well.. I don't know; just give it a try. niki_wiles 2016-02-17 14:23:41 UTC #3 Hi @majoritasdev Thanks, that looked really promising. I gave it a shot, but this - https://ads-api.twitter.com/0/stats/accounts/18ce53ur22q/reach/campaigns?start_time=2016-01-06T00:00:00Z&end_time=2016-01-07T00:00:00Z&campaign_ids=3x9tp .. seems to produce the https://twittercommunity.com/t/protocol-error-when-requesting-campaign-reach/61547 same problem majoritasdev 2016-02-17 14:44:42 UTC #4 @niki_wiles: what is your account timezone? If it's not UTC, then those dates are not midnights. They should be midnights in your account's timezone, expressed in UTC. For example: if my account timezone is "Athens, Greece" then start_time should be 2016-01-05T22:00:00Z and end_time should be 2016-01-06T22:00:00Z, since Athens, Greece is in UTC+2 hours. niki_wiles 2016-02-17 15:37:22 UTC #5 Thanks again @majoritasdev. The account timezone is set to GMT, so I guess that would be the same as UTC. majoritasdev 2016-02-17 15:51:00 UTC #6 Yes. I see. Then, I don't know. Twitter staff? brandonmblack 2016-02-22 22:59:34 UTC #7 @niki_wiles There's nothing obviously wrong with you request in terms of usage. Additionally, I'm able to successfully execute this request with twurl (see below): twurl -H ads-api.twitter.com "/0/stats/accounts/18ce53ur22q/reach/campaigns?start_time=2016-01-06T00:00:00Z&end_time=2016-01-06T23:59:59Z&campaign_ids=3x9tp" { "errors": [ { "code": "FEATURE_NOT_AVAILABLE", "message": "The account does not have the feat
needs to be fixed asap 9 votes Vote Vote Vote Vote Sign in prestine Your name Your email address Check! invalid email (thinking…) Reset https://tweetcaster.uservoice.com/forums/83503-tweetcaster/suggestions/2061151-fix-the-protocol-error or sign in with UserVoice password Forgot password? Create a password I agree https://en.wikipedia.org/wiki/List_of_HTTP_status_codes to the terms of service Signed in as (Sign out) Close Close 1 vote 2 votes 3 votes Remove votes You have left! (?) (thinking…) goofy_rika_89 shared this idea · July 21, 2011 · Delete… · Admin → completed · Mike responded · June 13, 2013 Please update to TweetCaster 7.5.1 through Google internal server Play. Show previous admin responses (1) completed · AdminTweetCaster (Product Manager, TweetCaster) responded · August 09, 2011 This issue was fixed in the 3.4 release. Tweet 23 comments Add a comment… Sign in prestine Your name Your email address Check! invalid email (thinking…) Reset or sign in with UserVoice password Forgot password? Create a password I agree to the terms of service Signed in as (Sign out) internal server error Close Close Post comment Submitting... ayonk commented · December 17, 2013 08:40 · Delete… I have installed tweetcaster on my torch 9860 and it always say protocol error has occured code 401 gone. Can u help me out with this please? Anonymous commented · September 24, 2013 06:21 · Delete… I am not able to post anything from my mobile and can do from laptop, I am using tweetcaster, its giving protocol error 400 ! please help me out... shinjirei commented · June 18, 2013 08:23 · Delete… some protocol error thing abt API version when i try to tweet a picture. works fine with text. please fix it. thanks. luggianni commented · June 17, 2013 11:32 · Delete… I have the same error but running on BlackBerry Anonymous commented · June 13, 2013 16:13 · Delete… Since yesterday, I have been unable to access/view my timeline. Error message indicates the need for V.1? When I look to update, unable to find any updates. I also logged out, then tried logging back in. Now, I am also unable to log in! Very frustrating! Lastly, I don't recall receiving any notification regarding any updates or changes to service. I
referer DNT X-Forwarded-For Status codes 301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable For Legal Reasons v t e This is a list of Hypertext Transfer Protocol (HTTP) response status codes. It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes. The first digit of the status code specifies one of five classes of response; an HTTP client must recognise these five classes at a minimum. The phrases used are the standard wordings, but any human-readable alternative can be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).[1] The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[2] Microsoft IIS sometimes uses additional decimal sub-codes to provide more specific information,[3] but not all of those are here (note that these sub-codes only appear in the response payload and in documentation; not in the place of an actual HTTP status code). Contents 1 1xx Informational 2 2xx Success 3 3xx Redirection 4 4xx Client Error 5 5xx Server Error 6 Unofficial codes 6.1 Internet Information Services 6.2 nginx 6.3 Cloudflare 7 See also 8 Notes 9 References 10 External links 1xx Informational[edit] Request received, continuing process. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 client except under experimental conditions.[4] 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers