Authentication

Authentication Type

Bearer token authentication is used to ensure only relevant DealTrack customers can access and read information from the DealTrack API. In order to retrieve data back from any DealTrack API endpoint, a valid JSON Web Token (JWT) must be passed on every request.

Generating a JWT Token

This JSON Web Token (JWT) can be generated by passing access credentials to an endpoint at oauth2/token. The token endpoint expects the user to post the following as form data:

• ClientId
• ClientSecret
• Scopes
• RegistrationId

ClientId, RegistrationId

The RegistrationId and ClientId are Universal Unique Identifiers which will be provided to you when Enable provision the API for you. They are used to uniquely identify you and your DealTrack client instance.

ClientSecret

The ClientSecret is the password you provide to the API to verify your identity, this will be provided to you securely when Enable provision the API for you. Since the ClientSecret is a password it must be stored securely and only shared with trusted parties.

Scopes

The bearer tokens can be used to give selective access to different parts of the DealTrack API. This is achieved with Scopes. When requesting a new token from the API you must include the scopes that you require access to. If your credentials permit access to those areas of the system, then a token will be returned that can grant access to the endpoints that return data from that part of the system.

There are currently three scopes. They provide read access to deals, activity logs, and users respectively.

• read:deals
• read:activity
• read:users

If you want to request data from the Deals endpoint, for example, then the read:deals scope must be included in your token. If you do not have the read:deals scope, then you will not be able to access the Deals endpoint.

Multiple scopes can be requested for a single token. The value of the scope parameter is expressed as a list of space-delimited, case-sensitive strings.

Example

A code example has been provided below for how to request an authentication token. The following form data is included within the example.

httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/x-www-form-urlencoded"));

var httpContent = new FormUrlEncodedContent(new Dictionary<string, string>
    {
        { "ClientId", "07E965CC-2425-44C6-88D8-9A694C30CCAA" },
        { "ClientSecret", "PelLobiJuumPwCUMDalM0AD0bzCDDciEMqFv6Bno" },
        { "Scopes", "read:deals read:activity" },
        { "RegistrationId", "688B42F8-60C8-4556-9912-0CD5E69C83D7" }
    });

var responseMessage = await httpClient.PostAsync("https://api.deal-track.com/oauth2/token", httpContent);

Token Authentication Response

If a token is requested using valid credentials you will receive a response in the following structure:

{
    "accessToken": "[token string]",
    "expiresIn": [time in seconds]
}

The “accessToken” is the string you will need to pass to the DealTrack API as the Bearer Token value for any subsequent requests. The “expiresIn” value is the time left in seconds until the token expires. After this time the token will stop working and it will be necessary to request a new one.

Using the JWT Token

Once requested, the token can be stored locally and used until expiry. For every request, the DealTrack API endpoints require users to set the Authorization mode to “Bearer” and set the value to the accessToken. This can be done by adding a Header named “Authorization” with a value of Bearer {bearer-token-string}