Skip to content
This repository has been archived by the owner on Sep 8, 2023. It is now read-only.

Rate Limited/Suspended? How to avoid? #25

Open
dezerving opened this issue Jul 13, 2023 · 5 comments
Open

Rate Limited/Suspended? How to avoid? #25

dezerving opened this issue Jul 13, 2023 · 5 comments
Labels
question Further information is requested

Comments

@dezerving
Copy link

Anyone getting rate limited/suspended on Threads (and since they're linked on Instagram too)?

Is the true limit actually 200 requests per hour? That is laughably low if true.

@LilaRest
Copy link

Hi, I've been suspended but using https://github.com/junhoyeo/threads-api , I'm very surprised as I hadn't performed much requests :o

@dezerving
Copy link
Author

Hi, I've been suspended but using junhoyeo/threads-api , I'm very surprised as I hadn't performed much requests :o

Seems like the limit is pretty low and makes it unusable for most tasks. Wondering how others are using this and avoiding bans?

@junhoyeo junhoyeo added the question Further information is requested label Jul 16, 2023
@drunkleen
Copy link
Contributor

The primary reason for this is the excessive generation of new tokens within a short time frame, such as multiple times per hour.
To avoid being suspended or blocked by Instagram, it's better to refrain from requesting a new token every time the API is used. It is more efficient to utilize the same token for next tasks as long as the token remains valid after the initial authentication.

@LilaRest
Copy link

The primary reason for this is the excessive generation of new tokens within a short time frame, such as multiple times per hour. To avoid being suspended or blocked by Instagram, it's better to refrain from requesting a new token every time the API is used. It is more efficient to utilize the same token for next tasks as long as the token remains valid after the initial authentication.

Note that in my case I was already caching the auth token.
A conversation has been opened here: junhoyeo/threads-api#143

1 similar comment
@LilaRest
Copy link

The primary reason for this is the excessive generation of new tokens within a short time frame, such as multiple times per hour. To avoid being suspended or blocked by Instagram, it's better to refrain from requesting a new token every time the API is used. It is more efficient to utilize the same token for next tasks as long as the token remains valid after the initial authentication.

Note that in my case I was already caching the auth token.
A conversation has been opened here: junhoyeo/threads-api#143

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants