Skip to content

Credentials

linvi edited this page May 8, 2015 · 21 revisions

Overview

Twitter execute queries against credentials that are stored as OAuth Tokens. These tokens allow Twitter to identify the Application that want to execute an operation on behalf of a specific User.

It is important to be aware that each query executed against the Twitter REST API or Stream API requires a WebRequest to contain credentials information in the headers.

The credentials information can be divided into 2, the Application Credentials and the User Credentials.

Application Credentials

Application credentials are generated by Twitter on its apps website.

After creating your application, the interface will show you a Keys and Access Tokens which will contains the magical information we are looking for.

  • Consumer Key (API Key)
  • Consumer Secret (API Secret)

User Credentials

When a user wants to use an application, Twitter generates a second pair of credentials that will be specific to an application.

For testing purposes, the apps website give you the possibility to generate such credentials. The generated credentials will be related to the User who owns the application.

Most application requires to get other users credentials information. Twitter provides 2 solutions to generate credentials for a user. You will be able to get more information in Authentication.

The user credentials contains the 2 following keys:

  • Access Token
  • Access Token Secret
Clone this wiki locally