Signing requests

Calculate the Authorization signature for API requests.

Once you have obtained temporary credentials, you will use them to compute the Authorization signature for all additional requests to the API.

Sample temporary credentials

    "accessKey": "***********",
    "secretKey": "***************************",
    "sessionToken": "FQoDYXd//////====ONCXz6OZC6FIxoWO1CGxVkwnY6WT07ZdLgGkr5ZkRCnGpa5uiF5KKbgMMWyQjKIazeyarBvXleDQmJznO4tBKq3U709cY20lVkdzHwAJQ5HXWHVop6w6cRy8uyOFPZ9fPD79PJ0L9KUkSo9uIG8DUK7PRvs4eAtIQQFdW+j2eHx6sUlF====34098qojfaof",
    "expiration": "2018-01-01T00:00:01+00:00"

Rightsline utilizes Amazon’s API Gateway and authenticates all calls by leveraging both STS and AWS Signature V4. Instructions for computing the AWS V4 signature can be found here.


Although you can construct this request by following the instruction contained above from Amazon’s documentation, Rightsline recommends you utilize the instructions at, which will speed up the process quite a bit.

Postman generates the HTTP Request in the required canonical format, including the code for signing a request in various languages:

For your implementation, you will need to generate your Signing Key programmatically (Postman is doing it for you in the background). Instruction for calculating the AWS4-HMAC-SHA256 signature can be found here: There are also great examples of how to generate the signature in various programming languages located here:

HTTP request example

  1. HTTP Request Method (GET, POST, PUT, etc.) + Canonical URI + HTTP Protocol (HTTP/1.1)

  2. Div API Key; unique to each Rightsline environment

  3. Requested host URL, which will change depending on the API environment ris[-staging, -int, -pm]

  4. Date/Time of the request in Amazon’s required format YYYYMMDD’T’HHMMSS’Z’ (

  5. Authorization Header with calculated Signing Key. (

Last updated