Getting 420 code but rate limits are fine

[ikoichi]

Hi,

I’m getting a 420 response status on the endpoint /1.1/direct_messages/events/new.json

I checked the rate limits using the endpoint 1.1/application/rate_limit_status.json?resources=direct_messages and they are all fine.

I’m using a per-user approach with my app.

What should I do and how can I check what happened? — Thanks

[gauloics]

It looks like the error code 420 is not about the limit you are requesting at the direct message endpoint, But it’s related to connection too often.

The client has connected too frequently. For example, an endpoint returns this status if:

• A client makes too many login attempts in a short period of time.
• Too many copies of an application attempt to authenticate with the same credentials.

You can read this information at https://developer.twitter.com/en/docs/twitter-api/v1/tweets/filter-realtime/guides/connecting