Open dezerving opened 1 year ago
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
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?
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.
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: https://github.com/junhoyeo/threads-api/issues/143
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: https://github.com/junhoyeo/threads-api/issues/143
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.