We require OAuth Authentication for user specific activity, including check-ins, prediction picks, and shout activity. We currently provide OAuth version 1.0a.
The general flow is similar to that which is laid out in this Yahoo! OAuth flow diagram.
|When you register your application, we will supply you with an oauth_consumer_key. This is also the same key used for non-oauth calls, passed in as a consumer_key parameter.|
- Get Request Token
- Redirect user to the Authorize URL which includes the authorization parameter
- For native apps, you can either implement a callback url on a server of your choice, or use our own internal callback for apps on iPhone/Android/iPad/GoogleTV/etc. See the Non-Web OAuth Verifier section on this page for more details.
- For web, you will be sent to the redirect url you specify during the request_token call, otherwise it uses the default callback you setup when registering your app
- Finally, you can request the access token to be used to sign oauth calls
Register Your Application
Fanvibe OAuth URLs
Non-Web OAuth Verifier
If using the oauth_callback_url is not possible, such as when iPhone/Android apps need to OAuth, we provide a callback that you can set when registering your app on http://fanvibe.com/oauth_clients. The callback happens on the fanvibe.com domain, and your app would simply need to parse for an HTML element with id=“oauth_verifier”. That’s the oauth_verifier that you would need to finally get the user’s access token.
Callback page snippet to parse
<h1>OAuth details</h1> <p class="oauth_detail"> <strong>OAuth Token:</strong> <code id="oauth_token">OAUTH_TOKEN_HERE</code> </p> <p class="oauth_detail"> <strong>OAuth Verifier:</strong> <code id="oauth_verifier">OAUTH_VERIFIER_CODE_HERE</code> </p>