Hi. Is it only I that such a phenomenon occurs though remaining-hits of returning information seems not to be correct, and to differ from information that returns by the X-RateLimit-Remaining header about API of rate-limit-status? With this, I am embarrassed because it consumes API though there is a method of seeing the X-RateLimit-Remaining header when the method of limiting API is issued, too.
- [twitter-dev] account/rate_limit_status API probrem moz