EviscapeAPI
7 Followers

Quick Links

View

Authors
(4)

Eviscape OAuth has adopted OAuth 1.0a. We have found XSRF bug with our Authentication mechanism. We have fixed it as per OAuth advisory.

Developers:Now you can register your application with "callback" and default "permission" parameters, they'll be override by "oauth_callback" and "perm". You may also edit your existing applications and provide this parameters. In other changes, We'r now only accepting "oauth_callback" while asking for request token.

Users:We have adopted "verifier" mechanism which means, if there is no callback then we'll display verification code on screen which you might needed for application which made request to access you account.

Use token and secret from above response and make an authorization call <span class="http-markup"><a href="http://www.eviscape.com/oauth/authorize" rel="nofollow">http://www.eviscape.com/oauth/authorize</a></span> for write access(?perms=write) you can also make a request for read access only with your oauth token and secret which you obtained in step 3.

Finally If User approves, then You can exchange your oauth_token with access_token which you'll be using in making authenticated API calls.