ver. 1424 (14cdcbf)
Authorize the Request Token
Unlike other methods, the authorize method is to be executed inside the User's browser. Consumer's role is to redirect the User to this URL, then wait if he ever comes back with a callback request.
Once the User is redirected to this URL, several things will happen:
|oauth_token||required||Consult OAuth 1.0a documentation for details.|
Default value: minimal
Currently, one of the following values:
Pipe-separated list of ISO 639-1 language codes. This indicates the order of preference in which the language will be chosen for the authorization page.
By default, OKAPI will display the page in the primary native language of local Opencaching installation.
|No additional authentication parameters are required.|
Technically, an HTTP 302 Redirect - it will direct user's browser to the OKAPI apps authorization page.
Whether with callback_url or with a manual user entry - you will get your oauth_verifier, which allows you to continue the 3-legged authentication dance.
If you used callback_url, you should wait for an HTTP GET request, with one additional GET parameter appended:
OR, in case when user denied the request: