#1

Hey,

I’m the developer of a third party Twitter client called harpy (harpy_app on Twitter).
Recently my API access got restricted multiple times due to it ‘violated Twitter Rules and policies’, prompting me to create a new API key just to have it restricted a few days later.

I’ve sent a support Ticket to ask for the reason every time and got a response once which claims the reason for the restriction were due to ‘spamming @ mentions’. Follow up questions to the support were left unanswered.

After searching online, this seems to be a common reason for developers to have their access restricted.

My question is, how can I as the developer of a third party Twitter client prevent this issue from reoccurring?
Is it possible to get whitelisted to avoid these restrictions?

cc @jessicagarson

Best Regards
Roberto

1 Like
#2

@rbydev, No one ever replied to this post here. Did you ever get an answer? I am about to post on this same topic. It’s just strange that this happens to so many, but it’s not discussed here.

#3

@Shoq
As it turns out your api access can be restricted if a user that is authenticated with your api breaks the terms of service or misbehaves in some ways.
In my case a user apparently was spamming @ mentions to others, which restricted api access to the whole app for all users.

#4

We have experienced the same thing recently.
There’s a real issue here with the way Twitter is handling these imo. Abusive users lead to blocked apps. If their API would allow some level of control it would be a different conversation, but the suggested solution by Twitter was only allowing mentions to accounts that have previously mentioned the user.
I’ve started a thread here to ask for a better way of controlling spammy accounts.