Using OAuth

Introduction

Understanding the way OAuth works can help create and debug applications which use Twitter’s API. To use OAuth, an application must:

• Obtain access tokens to act on behalf of a user account.
• Authorize all HTTP requests it sends to Twitter’s APIs.

The following pages will cover exactly how to obtain authorization through OAuth. If the process sounds like it is beyond the scope of your integration, consider using Web Intents, which do not need to use access tokens to interact with the Twitter API.

Client libraries

Most developers will not need to work with the details of OAuth, since Twitter Client Libraries already implement the protocol. It is strongly recommended to use one of these libraries.

• Twitter libraries with OAuth lists libraries known to work with Twitter.
• Single user OAuth with examples shows code examples for some libraries.

More information

• OAuth FAQ for questions which are asked frequently.
• Which authorization path should I choose? for more details about supported authorization methods.
• The application permission model for information about setting permissions for your applications.
• OAuth Echo for allowing 3rd party sites to post on your application’s behalf.