DQE Oauth2 solution architecture
The DQE OAuth2 API works via "REST" calls: in other words, HTTPS requests receiving responses encoded in JSON or JSONP.
Each call to our web services is described in this documentation. On request, we can provide you with a swagger describing these calls to our web services.
In our case, the authentication type is "server" to "server".
Find below our call pattern:
DQE Authentication platform
All calls will be made by acquiring a token as follows:
Calls to our webservices are made via the "GET" or "POST" method to a secure URL. There are different URLs each corresponding to the different available commands of our API.
Use of the token in DQE Saas calls
The use of the token is the same as in the case of a classic license: simply fill in the "License" parameter with the token.
If we take the example of the "CP" call (postal code method in funnel mode of the address):