Error 401 Test Screening

Hi Mehran Khan,

I am using Postman, I loaded the postman example pack that appears on the page, filled in the environment fields as indicated in the manual, then loaded the api to get the "{{protocol}}}{gateway-host}}{{gateway-url}}}groups" and it works fine.
With the group code, I finished filling in the fields to execute a simple synchronous case "{{protocol}}{gateway-host}}{{gateway-url}}cases/screeningRequest" and this is the one that returns 401.

Fill in the GroupID field with X, I don't know if it can be misused.

Metod: Post

{{protocol}}{{gateway-host}}{{gateway-url}}cases/screeningRequest

Body

POST /screeningRequest HTTP/1.1
Host: https://rms-world-check-one-api-pilot.thomsonreuters.com/v1/cases
Date: Thu, 19 Nov 2020 14:07:14 GMT
Content-Type: text/plain

{
"groupId": "XXXXXXXXXXXXXXX",
"entityType": "INDIVIDUAL",
"providerTypes": [
"WATCHLIST"
],
"name": "putin",
"secondaryFields": [],
"customFields": []
}

Answer

POST https://rms-world-check-one-api-pilot.thomsonreuters.com/v1/cases/screeningRequest401223 ms

POST /v1/cases/screeningRequest HTTP/1.1

Date: Thu, 19 Nov 2020 16:25:36 GMT

Content-Type: text/plain

User-Agent: PostmanRuntime/7.26.5

Accept: */*

Postman-Token: 9510a3e8-02d8-4dc8-8571-5e6e4aeb797d

Host: rms-world-check-one-api-pilot.thomsonreuters.com

Accept-Encoding: gzip, deflate, br

Connection: keep-alive

Content-Length: 200

{

"groupId": "XXXXXXXXXXXXX",

"entityType": "INDIVIDUAL",

"providerTypes": [

"WATCHLIST"

],

"name": "putin",

"secondaryFields": [],

"customFields": []

}

HTTP/1.1 401 Unauthorized

Strict-Transport-Security: max-age=15552000, includeSubdomains

Authorization: WWW-Authenticate: Signature realm="World-Check One API",algorithm="hmac-sha256",headers="(request-target) host date content-type content-length"

Transfer-Encoding: chunked

Date: Thu, 19 Nov 2020 16:25:37 GMT

Server: ""