#1

Hi,

An app of ours (app id 1272738) had its elevated POST rate limits approved a good while ago, but in practice we are still receiving app-level rate limits when our users try to follow others.

This has impacted a lot of our users, and we are overwhelmed by support requests and complaints. All follow requests come from direct user action as per the twitter policy. No automation.

Would someone be kind enough to actually push the ‘Approve’ button for elevated POST access’ on our app?

App ID: 1272738

Thanks!

–
Gurpartap Singh

Elevated POST Limit Increase?
App wide friendships/create rate-limit issue
IP addresses/subnets getting blocked for using follow api
#2

There appears to be some issue wrt elevated POST access.

Every day since the past 2 weeks, the API appears to be limiting us at random arbitrary limits (e.g. 1451, 397, 412, 1178, etc), which are some times less and some times more than the daily app limits for follow endpoints (1000).

It almost seems like some rate-limiter services in front of the twitter api are not aware of “elevated” access for some of us (as there are a few other developers reporting this issue as well).

Although we’ve had elevated POST access for over a year now, I reapplied for the same about 10 days back and haven’t heard back by email either.

Case# 0129069096 [ref:00DA0000000K0A8.5004A00001nCOw0:ref]

I would really appreciate some communication on this.

Best,

Gurpartap Singh

#3

Our users are still facing this error on “most” of their follow requests (since about 10th/11th October). It does not stop at the advertised 1000 per day app limit (so it might not even be related to elevated POST access – which we have already had for over a year now).

Is this issue even in anyone’s notice in the API team? :confused:

#4

The elevation for POST relates to sending Tweets at an app level. There’s no change to the user account follow limits.

#5

Thanks for the response, @andypiper.

Does it matter that we process all api requests on the server (with a few fixed ip addresses), rather than on user’s device?

The error code is 161 on /friendships/create.json?user_id=%d&include_entities=true&skip_status=false.

#6

Hmm. I thought the POST limits applied to follow endpoint as well.

#7

This may be my mistake; I’ll have to check into this tomorrow. I wasn’t aware that any user could follow over 1000 users in a day and that would not be very organic behaviour regardless.

2 Likes
#8

Individual users are still limited to 400 follows per day. The 1000 follows “per app” limit is across all users. No single user is able to cross 400 follows regardless of app limit or elevated access of app.

Any how, re the issue at hand, we began seeing follow errors (code 161) on 11th Oct ‘19 UTC. Follow requests get accepted at random until some arbitrary number, after which only a few requests would pass. On most days, thousands of our users are barely able to cross 300 or 400 follows collectively before the error begins to stop them. On some rare days, our activity logs show 1000 to 1500 successful follows across all users.

Let me know if you need more info from me.

#9

Were you able to look into this? I would really appreciate a remedial action.

Here’s how I understand limits to work:

  • The API rules let individual users make 400 follow requests per day (across all apps I believe).
  • Apps without elevated-POST-access are able to request max 1000 follows a day collectively for all its users.
  • Elevated-POST-access lifts this collective limit for the app (while each of app’s users are still restricted to max 400 follows a day).

Here’s what isn’t working:

  • Twitter API is limiting (error code 161) our collective follows to a random number every day. For example: 1451, 397, 412, 1178, etc.
  • After this arbitrary limit is crossed, a very limited number of follow requests seem to succeed.
  • We have elevated POST access.
  • App ID: 1272738
#10

Any update on this? :smiley:

#12

POST elevation does not in any way affect the follow limit Twitter has in place. As stated here, this is true for all users on the platform. There is no way to get an elevation to follow more users.

There are additional limits around how many follows you can create. For example, if you hit a follow limit:

You may encounter a message that states, “You are unable to follow more people at this time.” You’ll encounter this message for one of the following reasons:

  • You’ve reached the daily follow limit. You can follow more accounts after a day has passed.
  • You’ve followed too many accounts too quickly. Try again in an hour or so.
  • You’ve hit a follow ratio limit. You can try again once your account has more followers, or you can unfollow a few accounts to follow new ones.
#13

Thanks for the response, @Hamza.

I believe I’m being misunderstood. I’m not asking to be able to follow more than what is allowed of any account (400 per account per day, etc).

What I’m reporting here appears to be an issue with the API/follow limit logic, rather than my misunderstanding about limits. I don’t know if elevated POST access has anything to do with it.

I am encountering limit errors through my app even on regular twitter accounts that haven’t followed a single person in days (from any app), which is certainly unusual.

#15

For this specific issue, I believe this may be isolated to your app as I’m not able to replicate. I’d advise you contact Twitters API Policy team here to see what’s going on and get it corrected ASAP.

#16

I haven’t heard back from them, which is why I thought of posting on the forums. Would it be possible to nudge them?

I reached them out on 2019-10-13 through “I would like to apply for elevated POST limits.” option along with all the details.

Case# 0129069096
ref:00DA0000000K0A8.5004A00001nCOw0:ref

#17

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.