OAuth2 Authentication Guide for Data as a Service

OAuth2 Authentication Guide for Data as a Service

Requesting a Token

Requesting a Token

There are four different ways to request an access token but they all accomplish the same thing. An example of each is given below, and the end user is free to use whichever one works best for them. Note that the credentials in these examples are not valid and the user should substitute their own valid credentials for the calls to work.
There are two different ways to authenticate when requesting a token. There is the standard
user name / password
combination, or alternatively the
user name / license key
combination. The license key option is typically used if you have purchased more than one license for the same product and need to specify which one to use. For example, some customers have a single account with one Email Verification license key for their Marketing department and another for their Sales department. If that customer authenticated with a user name / password, the DaaS system has to guess which Email Verification license to use for the transaction. By providing the license key there is no question of which license to deduct transactions from.
There are examples of both authentication methods included below. Please note this difference in authorization between the two methods when using OAuth2:
  • When authenticating with a user name / password combination, the resulting token is valid for any license in that account.
  • When authenticating with a user name / license key combination, the resulting token is valid for only that specific license.

0 COMMENTS

We’d like to hear from you!