22
edits
Changes
+much more detail
== Creating a new app ==
=== BEFORE creating an app: Bot-specific stuff === If you're going to have a separate twitter account for your bot, the best thing to do is to create that account ''before you create your app''. Then create your new app under ''under the bot's account''. This will simplify doing the OAuth dance below. === First steps to create an app ===
* https://dev.twitter.com/apps/new
* sign in with your twitter (bot's) account
* fill out basic info about your app
* agree to be a good citizen, as detailed below
=== Setup Set up the App ===
* after you've set up your app, you receive your OAuth consumer keysfor the app:
** '''<tt>consumer_key</tt>'''
** '''<tt>consumer_secret</tt>'''
You can also fill in the rest of the self-explanatory fields in the Details and Settings tabs as you like (organization, etc).
While still logged in under the bot's account, navigate to the app's page and generate your access token:
=== General Rules of the Road == === General Rules of Conduc and TOS ===
* https://dev.twitter.com/terms/api-terms
=== Rate limits ===
* REST api is limited to...** 350/reqs per hour ''per signed-in account''** 150/reqs per hour ''per anonymous IP address'' Things that '''do''' count against your limit Things that '''do not''' count against your limit* checking the rate limit (it can change, though nowadays it rarely does)
=== Other gotchas ===
* Repeated tweets
* failed reqs
== General things you may want to do ==
=== Check for @-messages and reply ===
=== Tweet updates from elsewhere ===
