Authentification Pre-requisite

Using a token generated on your side

Adways APIs are configured to be secured. An Adways user can be identified through multiple Authentification methods.

To be Adways Authentification compliant, you must use authentification token mechanisms based on access_token such as OAuth2.

Before making a request using your tokens, Adways has to perform a preliminary integration task. To retrieve information about the user using your token, you first need to provide Adways with a request/API.

For example, you generate a token for your user on your platform:

access_token: 02e6e0b90116a3bb566c54e44553f071f3dda8f0

If you want to be able to make a request using this token to our APIs, you must set your Authorization header like this:

Authorization: Bearer 02e6e0b90116a3bb566c54e44553f071f3dda8f0

Once your tokens support integrated on our APIs, Adways will give you a constant, such as: 'TokenProviderConstant' that you will be able to add in your request headers.

Adways will provide you a specific client_id and client_secret. Those credentials will be used for the New user Registration

From this point, you can make requests to Adways APIs with full Authentification information:

    Authorization: Bearer 02e6e0b90116a3bb566c54e44553f071f3dda8f0
    X-Token-Provider: TokenProviderConstant

When Adways servers will receive a request containing your X-Token-Provider constant, Adways will retrieve user information from your side and compare it with its own information.

Using adways client_id and client_secret

If the user has an adways access he can retrieve his client_id, client_secret. Using thoses informations you are able to sign your requests using the "Basic" authorization method.

    Authorization: Basic client_id:client_secret

With this method you can't perform the DELETE method in adways's APIs.

To get an example of a basic request using these headers (checking if the user on your side is known by the Adways platform), please refer to: User validation test