0
Fixed

Twitter rate limit exceeded

Trevor Green 2 years ago • updated by Vladimir Mullagaliyev (co-founder) 2 years ago 1

When marking Twitter comments as "reviewed" in the Agent Interface, we get an error message quite often that says { "errors": [ { "code": 88, "message": "Rate limit exceeded" } ] }.


My speculation is that perhaps you are using application authentication instead of our user token? I'm thinking this because I don't really see how we can hit the 180 request rate limit for a user token, though it is quite possible to hit the 450 request rate limit globally.


Maybe my speculation is wrong, but we do see the rate limit errors quite frequently.

Answer

Answer
Fixed

Hello Trevor,

We used to use our common oauth key and secret for all projects. So, the limit worked for all projects summary.

Now we've changed it and each project use his own oauth key and secret.

Please check again. The problem could be fixed.

GOOD, I'M SATISFIED

Thanks Vladimir


The problem seems to be fixed. Much appreciated :)

Satisfaction mark by Trevor Green 2 years ago
Answer
Fixed

Hello Trevor,

We used to use our common oauth key and secret for all projects. So, the limit worked for all projects summary.

Now we've changed it and each project use his own oauth key and secret.

Please check again. The problem could be fixed.