We consume DirectMessageList from twitter4j api for our authenticated and verified use-case. We use rateLimitStatus field to determine how much time do we have to wait for hitting twitter API next.
As of now, it has started coming as null from twitter end. Please check, what were the changes and were they informed by some medium.
rateLimitStatus in twiter4j is derived from the http headers, but there’s also a separate call to http://twitter4j.org/javadoc/twitter4j/api/HelpResources.html#getRateLimitStatus-java.lang.String…- you could use - this has a Map of resources and limits
To debug, i’d try making the same call with twurl https://github.com/twitter/twurl twurl -t ... and see what http headers are being returned - or try to override twitter4j http handler to output some mode debug logs
Hi,
I too noticed a changed since yesterday, where the headers x-rate-limit-* are no longer returned when using GET /1.1/direct_messages/events/list.json
Is it wanted? Was it announced? I’m using twitter4s and it requires these headers to work
1 Like
Hello everyone. Just to say that I’m checking into this internally, I’m not certain of any change here, but several of you are reporting a difference, and that seems to be something worth investigating - thank you. Unfortunately I also cannot commit to a specific timescale for follow-up, but know that this is something that we are aware of.
2 Likes
system
closed
#7
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.