If you have an app or service that needs to be interacted with WHASOLS on behalf of your users, you should use OAuth.

WHASOLS uses OAuth 2, an open specification, which makes its users to authenticate with WHASOLS to both verify their identity and give your app permission to access their data.

Once authorization is fulfilled by a user, the OAuth process returns or allows an access token to your app. This given access token is a string generated by the WHASOLS instance that you’ll need to send with each subsequent API request to uniquely clarify or identify both your app and the end user.

For OAuth using, there are several reasons we use. Noticeably important among them is , your app doesn’t require to store or transmit the user’s WHASOLS password. OAuth also allows the user to authorize only a limited or selected set of permissions and the user may ercall or abort access at any time. For your users experience, it makes OAuth a secure and more safe form of API authorization.

OAuth is an open protocol that is supported in WHASOLS for allowing third-party applications to obtain bounded access to the WHASOLS service on behalf of users.