Authentication

SECURITY

All Record requests are secured with a 128-bit security token that is assigned by SafetyChain and accessible via HTTP SSL protocol only. The security token is provided by SafetyChain during implementation. The token is validated for each request. SafetyChain supports creation of a unique token for each API or a common token that can apply to all APIs used by the customer. In addition, an optional IP White List to limit API access can be defined as well.

REQUESTS

To authenticate all requests, a security token must be provisioned by SafetyChain support.

📘

Note:

Each Security Token should be used on a per user basis and not shared

This token will be used as a query parameter (ST); see example below.

/clientapis/v1.0/setCache?ST=b308957c770249c4acc6004009555952

For requests that fail to authenticate, you will receive the following response -

STATUS: 200 OK

{
  "data": [
    {
      "ErrorMsg": "User Not Authorized or is over their quota"
    }
  ]
}