#1

My app posts updates to a number of different Twitter accounts. Periodically though, the app receives a 403 error back from the Twitter API, and the impacted Twitter account then requires a manual sign in to reactivate access via the API.

I’ve adhered to the guidelines that state it should be apparent from the Twitter profile that the account is automated / a bot.

How can I go about ensuring the Twitter accounts that my app uses, do not keep getting blocked from API access in this way?

This is the screen I get when I log in manually following this issue occurring:

What happened?
To make sure Twitter is as safe as possible, we might occasionally ask you to verify you’re not a robot.

What next?
To get back to the Tweets, select Start to verify you’re really human.

I then have to go through “I’m not a robot” and it unblocks it for me.

I understand Twitter isn’t against bots providing their guidance is followed.

Thanks

#2

@NotTea I saw you posted a similar question here: Spike of 403s account locked for users

Did you ever find any luck getting this resolved?

Thanks!

#3

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