RateLimits strikes back! Following the rate limit post I made yesterday, I am writing another post to get even more information concerning the RateLimits.
I have 2 questions, one concerning the destroy methods and one concerning RateLimit that I could not map to endpoints.
All the destroy queries seems to be rate limited as per the documentation (e.g. https://dev.twitter.com/rest/reference/post/direct_messages/destroy).
But I have not been able to find any rate limit documentation concerning their values nor could they be found in the rate_limit_status.
Do you have any information concerning these queries?
WHERE IS THE RATE LIMIT’S QUERY?
I have been able to associate most RateLimit returned by the rate_limit_status to a query but I could not figure out, which URL the following were referring to.
- /account/login_verification_enrollment (I do not know what this is related with, as another RateLimit exist for VerifyCredentials
- /device/token (I tried calling https://api.twitter.com/1.1/account/update_delivery_device.json?device=none) without the rate limit being affected
- /direct_messages/sent_and_received (there already is one for each and neither getting the message sent or received seems to affect this value)
I know this is a lot of information to ask.
Thank you for any help.