#3

Thanks a ton for that. :pray:t6:
Eagerly waiting.

#4

I don’t think you should delete the suspended program. You can only submit your application and wait patiently for the twitter staff to reply to your email.

#5

Whoops, whoopsies!

I already did, man. I didn’t know what else to do, and it was stressing me tf out.

#6

Very similar experience here. Wondering how you were posting tweets using your app - did you enable oauth1.0a to get a read/write token?

I could’t find a way to get an access token w/ write permissions without doing so, so I was wondering if that might be the reason…

#7

Yeah, I enabled read/write from the developer dashboard. I saw an article on here about it and followed its directions.

Basically, create your app, go to settings, scroll down to user authentication settings, create and turn on Oauth v1.1 toggle switch, select permissions level and fill the rest info. Then regenerate your access toketo reflect the new permissions.

#8

Please let me know if you have any luck with this - I’m getting the same problem - getting app banned with no explanation. I’m making a bot, not an app for end users.

I think this is something to do with the fact that the new API (v2) requires an app to look like it’s for end users in order to be able to post… @jessicagarson any news here?

#9

Just wait patiently for a reply. I was suspended on November 15 and reactivated on November 23. The main reason is that Twitter has an automated system that can batch find and disable the abuse of API keys. Unfortunately, your application seems to have strayed into one of these spam groups.

#10

SMH :man_facepalming:t6:. That’s a whole week. Well, Twitter does what Twitter does. Re: @jessicagarson

Meantime, I sent another ticket again. ID: 0245931388, and I’m familiarising myself with the API and writing some non-api requesting functions.

I would like to check out your bot. If you don’t mind.

#11

@bentbot, I don’t think I’ve checked in to see what might be happening on your end, is bentbot the handle you are using? Do you have the case number of any previous appeals?

#12

@thierryntoh24 I just checked with the team on your case, and I’ll let you know when I hear further. This does sometimes take some time on our end.

#13

Well, later is always better than never, amirite. :pray:t6:

#14

It’s @bentbot_ (with an underscore at the end).

The only thing I can think of that might have caused a flag is enabling oAuth1.0a in order to get a read-write access token (for my own account only) and having to enter nonsense URLs for the oAuth flow details (because no user will ever authenticate with the app, I just generate tokens via the developer interface for my own account).

If this is the case there needs to be a “safe” way for new apps to get a write token.

#15

@thierryntoh24, I talked to the team, and your account should be back to normal. Let me know if you are still having issues here.

1 Like
#16

Yeah wow! it is back to normal. Wuh!
Thanks a lot, @jessicagarson
どうもありがとうございます😊

2 Likes
#17

Hi @bentbot, I talked to the team, and they mentioned your account should be back in a normal state. Let me know if you are seeing something different.

#18

Just like that, magic. Thanks!

1 Like
#19

That is great.

#20

Hi @jessicagarson, I have sent a request for an Academic account, and after failing one time to get an account (my information wasn’t clear enough), I received an email saying my case is open again. However, after emailing Twitter again and also sending a message through the developer platform, I still see this on my project with no change:

image
image1389×638 29.6 KB

Could you please see if there is anything I should be doing? It’s been more than two months that I haven’t received anything from Twitter.

Thanks in advance!

#22

I can check in here. What username did you apply with?

#23

Hi @jessicagarson, thank you for your reply. Here is my username: @Mitra_Mir