- Accounts and users
- Direct Messages
- Publisher tools
- Twitter for Websites
- Developer utilities
- API reference index
Allows a Consumer application to use an OAuth
request_token to request user authorization.
This method is a replacement of Section 6.2 of the OAuth 1.0 authentication flow for applications using the callback authentication flow. The method will use the currently logged in user as the account for access authorization unless the
force_login parameter is set to
This method differs from GET oauth / authorize in that if the user has already granted the application permission, the redirect will occur without the user having to re-approve the application. To realize this behavior, you must enable the Use Sign in with Twitter setting on your application record.
|force_login||optional||Forces the user to enter their credentials to ensure the correct users account is authorized.||true|
|screen_name||optional||Prefills the username input box of the OAuth login screen with the given value.|
Send the user to the
oauth/authenticate step in a web browser, including an oauth_token parameter: