If you’ve ever been working on a Twitter application and thought to yourself “I wonder what it’d be like if Twitter suspended my API key” then wonder no longer! It takes the form of an email that looks something like this:
This is a notice that your OAuth token for [application name] has been suspended from interacting with the Twitter API.
Please make sure that your application follows Twitter’s policies, including the Twitter rules, the API rules, and the automation rules.
To request for your token to be re-enabled, please write to api@twitter.com
To which you might reply with something like this:
Dear Twitter API Gatekeepers and Gurus,
I’ve received a message that states “your OAuth token for [application name] has been suspended from interacting with the Twitter API.”
Here’s a link to my app details: [http-blah-blah-blah]
I read over the included links to the Twitter rules and the API rules, and glanced over the automation rules (the application I’m working on doesn’t automate anything, so I assume there’s little of relevance there). Still, I’m unable to determine which of the rules my application violates.
I’ll hazard a guess. Is it because the Callback URL for my app points to a location that is not publicly accessible? This is because I prefer developing on a local machine before putting my codes on the web. I didn’t see anything in the Twitter/API rules the said this was unacceptable, but I was a little drunk when I was reading them so it could have been missed.
At any rate, if the Callback URL is the issue, please let me know and I can correct it. Otherwise, if I could get a specific reason why my application OAuth token was suspended it’d be very helpful.
Thanks,
Beau
I’ll update when I have some more details about what’s going on and why.
Not really an update @ 2010.02.20: I still haven’t heard back from Twitter. I suppose my next course of action will be to register another app and continue work using the new information. Might as well set up a valid URI for it just in case.
