question

Upvotes
1 1 2 2

Error 401 Test Screening

I am testing with the API, performing a synchronous query, and I read each of the 401 error posts here, without achieving a solution.
I would appreciate your guidance.

The first error I noticed in my Postman was:
JSONError: No data, empty input at 1:1

Then I realized that the error itself is a 401 that says so:
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: Mon, 16 Nov 2020 22:56:27 GMT
Server: ""

I can't make any progress on the project and time is running out.


world-checkerrorscreeningscreening-apierror-401
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

@ignacio.valenzuela

Apologies for the delayed response, could you please share the complete request and response for the 401 that you're receiving?

Upvotes
1 1 2 2

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: ""



icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1.2k 4 1 2

@ignacio.valenzuela

Thanks for providing the details, let me know if we can get on a quick call and resolve this, I will send out an invite

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1.2k 4 1 2

@ignacio.valenzuela

Just checking to see if you still facing this issue and if you would like to get on a call and resolve this?


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.