Thanks Taylor, although it's odd because an app I've had live for many weeks has only just started erroring. I was fairly sure it was this. I will take a closer look.
On Oct 26, 11:00 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Hi Tim, > > POST actions aren't "rate limited" in the same way as GET actions in the > Twitter API. There are natural, organic (sometimes unpublished) limits to > some write operations. > > In this case, you're creating a new message, which isn't something rate > limited on the API level. If you were being prevented from sending > additional direct messages, you would get 403 Forbidden. > > Taylor > > On Tue, Oct 26, 2010 at 2:50 PM, Tim <fabianh...@googlemail.com> wrote: > > Authenticated calls to delete a direct message has no X-RateLimit- > > headers present. > > Sent and received headers below. Response body removed for privacy > > reasons, but the action was successful. > > I can replicate this at will, (for now) > > > > POST /1/direct_messages/destroy/1779991661.json? > > > oauth_consumer_key=0EUF35h2PDygBcgv8FUg&oauth_nonce=1288129484.629582&oauth_signature_method=HMAC- > > SHA1&oauth_timestamp=1288129484&oauth_token=16683251- > > > Mviy4G9b78DLESCW0eO8HZNLrNFMgMLTcDtY0CvYG&oauth_version=1.0&oauth_signature=48VkXPCGgRzViAMQtiaM4IUbzls > > %3D HTTP/1.0 > > > Host: api.twitter.com > > > Connection: Close > > > < HTTP/1.1 200 OK > > < Date: Tue, 26 Oct 2010 21:44:45 GMT > > < Server: hi > > < Status: 200 OK > > < X-Transaction: 1288129485-25373-41095 > > < ETag: "b74ad6bfd07d44b17d2f5f0616cc0ffa" > > < Last-Modified: Tue, 26 Oct 2010 21:44:45 GMT > > < X-Runtime: 0.18336 > > < Content-Type: application/json; charset=utf-8 > > < Content-Length: 2569 > > < Pragma: no-cache > > < X-Revision: DEV > > < Expires: Tue, 31 Mar 1981 05:00:00 GMT > > < Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, > > post-check=0 > > < Set-Cookie: k=78.86.231.80.1288129485059207; path=/; expires=Tue, > > 02-Nov-10 21:44:44 GMT; domain=.twitter.com > > < Set-Cookie: guest_id=128812948506442879; path=/; expires=Thu, 25 > > Nov 2010 21:44:45 GMT > > < Set-Cookie: lang=en; path=/ > > < Set-Cookie: > > > _twitter_sess=BAh7CToMY3NyZl9pZCIlOGMwNTIxYTIyN2U5MDE5YTVmYzYwMjFlOGRjN2M1%250AZTc6D2NyZWF0ZWRfYXRsKwgWGYDqKwE6B2lkIiVkMDVhODAyYmQwMWNmMzlm > > > %250AMDY4YTg5MjQ5YWE1MTZjOCIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6%250ARmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA > > %253D%253D--b8a42a512de56cb8c9591a9d91cffc1e86f15dd2; > > domain=.twitter.com; path=/ > > < Vary: Accept-Encoding > > < Connection: close > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
