Open main menu

Changes

C4LN 2012: Intro to the Twitter API

1,070 bytes added, 14:16, 24 May 2012
+more OAuth and setup details
* user (resource owner) -- ''user''
Credentials
* consumer credentials (consumer key & consumer secret)
* access credentials (access token & access secret)
* (also request token & secret)
* receive OAuth keys workflow:** user goes to server and says they'd like to authorize application ''<tt>consumer_key</tt>X'' to do action ''Y''*server generates access token which represents the combination of the specific app & the specific user & the specific level of access the user has granted to that app* user feeds the access token to the app* the app can then present the access token to the server (in combination with its consumer credentials) and be permitted to do whatever'''<tt>consumer_secret</tt>'''s been authorized
=== Setup ===
* after you've set up your app, you receive your OAuth consumer keys:
** '''<tt>consumer_key</tt>'''
** '''<tt>consumer_secret</tt>'''
 
The first thing you're going to want to do is go into your app settings and set the correct level of access that your app is going to request from users. This is under the '''Settings''' tab:
* tabs we're initially interested in: Details & Settings* Settings tab:** Application type:*** Read*** Read/Write*** Read/Write/Access DMs
You are probably going to want one of the latter two. Which one depends on whether or not your app is going to work with DMs (direct messages) or not.
You can also fill in the rest of the self-explanatory fields in the Details and Settings tabs as you like (organization, etc).
== Bot-specific stuff ==
Shadowspar
22
edits