Error while calling https://rms-world-check-one-api-pilot.thomsonreuters.com/v1/cases/screeningRe...
...quest
i am getting the below error for any Rest call done.
Below the message call
Request body
{
"caseId": "my customer ID",
"name": "John Doe",
"providerTypes": ["WATCHLIST"]
}
Request header
Signature keyId="3a38e8e6-7f64-42af-9dee-615e2cc93007",algorithm="hmac-sha256", headers="(request-target) host date content-type content-length", signature="RZuDd0rKv4mxpyMrMIP+c425a7o/6TpKP2N3DYfZTe4="
Best Answer
-
You're receiving a 401 Unauthorized cause the request you're passing is incorrect, it lacks details such as groupId and entity type, please use the below payload to successfully screen the entity, John Doe.
{
"groupId": "{{group-id}}",
"entityType": "INDIVIDUAL",
"providerTypes": ["WATCHLIST"],
"caseId": "my customer ID",
"name": "John Doe",
"secondaryFields": []
}0
Answers
-
But those fields are not mandatory and i am using the sample provided in the world check one api documentation.
Also i don't have access on the following URL https://rms-world-check-one-api-pilot.thomsonreuters.com
POST /v1/cases HTTP/1.1 Host: rms-world-check-one-api.thomsonreuters.com Date: Tue, 07 Jun 2016 20:51:35 GMT Content-Type: application/json Content-Length: 88 Authorization: Signature keyId="4321",algorithm="hmac-sha256", headers="(request-target) host date content-type content-length", signature="Iktz/AdXHmDouNm6uBB8ZW0xcfNGuWGDxmX9TFMwuF0=" { "caseId": "my customer ID", "name": "John Doe", "providerTypes": ["WATCHLIST"]<br>}0 -
Are you using postman?
0 -
Also i am still getting the same error after using the sample you provided above
0 -
Please find the snapshot from the documentation which states that the only caseId, custom and secondary fields are optional and details such as group Id, entityType, name and provider types are mandatory parameters to successfully screen, kindly try the payload that i provided earlier and let me know if you're able to screen.
0 -
No i am trying the call from my java application and not Postman
0 -
yes but secondary fields is optional
0 -
The reason your request is failing is cause the date value being passed is incorrect, the date value in your request is 7th Jun 2016 , ensure a correctly synchronized clock is used to generate request timestamps.
0 -
Yes, you can omit secondary fields and pass the remaining mandatory parameters, make sure that the date header value that you are
sending is in sync with the NTP or the GMT clock for the API call to succeed.
The difference with the API clock time shouldn’t be >30s. When it’s more
than 30 seconds you get a 401.0 -
This date was provided in the sample.kindly provide the date that needs to be used as per your GMT time zone
0 -
This date was provided in the sample.kindly provide the date that needs to be used as per your GMT time zone
0 -
Also does the signature mandatory?and what is the value expected for the groupid
0 -
The format of the date should be "Wed, 10 Apr 2019 08:12:21 GMT", please ensure that its synchronized with the GMT clock.
Yes its mandatory as it forms a part of the authorization header. Group Id value you can obtain by consuming the "SEQ-pre-groups: Get my top-level groups" API which should be the first API that must be called to fetch the group details.
0 -
I am already using this format for the Date with GMT clock and still getting the same issue.Concerning the group id,can i generate a sequential number from my end as the group id is a string value
0 -
Can you please provide me the complete request and response headers, you cannot generate a sequential number for the group Id value, group Ids are already available for your account which must be fetched from the API call I mentioned earlier. You're still getting an error even with the correct time format cause the group Id which is a mandatory parameter is not being passed. Let me know if you're facing dificulty in consuming the "SEQ-pre-groups: Get my top-level groups" API from postman.
0 -
i passed a dummy value now for Groupid and still getting the same error.Concerning the Above api from where i can get the call of this API
0 -
You cannot pass a dummy value, your groups have unique Ids assigned to them without which you cannot screen an entity, Kindly go through the quick start guide containing step by step guidelines on how to fetch the Top level group values.
https://developers.refinitiv.com/customer-and-third-party-screening/world-check-one-api/quick-start
0 -
As you suggested i checked the API under collection runner of postman,and found the below:
the request header is composed of 2 parameters Date and Authorization
the request body and response body are empty
Please advise what to send and provide a sample calling.below screenshot for your reference
0 -
Moreover after importing the json files in postman and as you can see below all the requests are given the same error i got : 401 unauthorized
0 -
Hi @abdulwahab
Have you added your API key & Secret to the postman? From the screenshot, I see that they are not added.
0 -
where i can add the pi key and the secret key and do i need to re-import the json files?
0 -
As shown in the screenshot, click the button highlighted in the red box and edit the API key & Secret values and add the respective key and secret to it.
0 -
this is what i get when i click on the mentioned button.there is no key or secret key section
0 -
Hello @abdulwahab,
Where you able to add your API key and secret as suggested above by @Mehran.Ahmed Khan?
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 698 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 2.9K Elektron
- 1.5K EMA
- 257 ETA
- 565 WebSocket API
- 40 FX Venues
- 16 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.1K Refinitiv Data Platform
- 799 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 232 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 101 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛
