Getting 400 bad request for v2/cases/screeningRequest

We are trying to hit the v2/cases/screeningRequest from our Haskell application. The request is made from a function called postWith. We are getting 400 bad request when request made from application whereas getting 200 response when request is made from Postman. The generated signature is same as with the postman signature when Date is hard-coded in postman. I also think the issue is not with the Date generated since it is also in sync with Postman generated Date.
I'm pasting the request headers and body here for your reference which I tried at 21.00 IST.
dataToSign:
"(request-target): post /v2/cases/screeningRequest\nhost: api-worldcheck.refinitiv.com\ndate: Tue, 22 Aug 2023 15:29:58 GMT\ncontent-type: application/json\ncontent-length: 237\n{\"caseId\":\"\",\"caseScreeningState\":{\"WATCHLIST\":\"INITIAL\"},\"customFields\":[],\"entityType\":\"INDIVIDUAL\",\"groupId\":\"5555555555555555555555555\",\"name\":\"John Smith\",\"nameTransposition\":false,\"providerTypes\":[\"WATCHLIST\"],\"secondaryFields\":[]}"
Authorisation header:
"Signature keyId=\"***\",algorithm=\"hmac-sha256\",headers=\"(request-target) host date content-type content-length\",signature=\"GF/aRq1tVSO/2M6pXzCkFvz+SomD3HIUWkZVbhlnZ78=\""
Request body:
{"caseId":"","caseScreeningState":{"WATCHLIST":"INITIAL"},"customFields":[],"entityType":"INDIVIDUAL","groupId":"***","name":"John Smith","nameTransposition":false,"providerTypes":["WATCHLIST"],"secondaryFields":[]}
All request headers:
headers = [(\"Host\",\"api-worldcheck.refinitiv.com\"),(\"Authorization\",\"Signature keyId=\\\"***\\\",algorithm=\\\"hmac-sha256\\\",headers=\\\"(request-target) host date content-type content-length\\\",signature=\\\"GF/aRq1tVSO/2M6pXzCkFvz+SomD3HIUWkZVbhlnZ78=\\\"\"),(\"Date\",\"Tue, 22 Aug 2023 15:29:58 GMT\"),(\"Content-Length\",\"237\"),(\"Content-Type\",\"application/json\"),(\"User-Agent\",\"haskell wreq-0.5.4.0\")]
This header is been taken from terminal so no need of worrying about the extra back slashes.
Note: the exact request body works on postman with same header even with the same useragent.
Best Answer
-
Hello @karthickumar1402 - thank you for reaching out. I have sent you an email, and will post any updates on this thread as soon as we can.
Blessings,
Judith0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 688 Datastream
- 1.4K DSS
- 624 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 692 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
- 121 Open DACS
- 1.1K RFA
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 10 Wealth Management Web Services
- 92 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛