Timeout error on calling screeningRequest API
Hello Team,
I've been exploring the World Check One API for sanction screening in the test environment. Thus far, I've successfully authenticated and connected to several endpoints, including those listed below:
- Step 1: Select an endpoint - /v2/groups
- Step 2: Choose a tool for your request - made requests to REST endpoints
- Step 3: Send your request and review your response - /v2/groups returned a status of 200
Currently, I'm attempting to connect to the cases/screeningRequest endpoint, but I'm encountering some challenges. The API is responding with a timeout issue, even though I have the timeout set to 30 seconds. When I remove the timeout parameter, I receive the response "Status: 0; Message: Empty reply from server".
Below is the JSON I'm sending. The same JSON works fine in POSTMAN:
{"groupId": "MY-GROUP-ID","entityType": "ORGANISATION","caseId": "","providerTypes": ["WATCHLIST"],"caseScreeningState": {"WATCHLIST": "INITIAL"},"name": "Apple", "nameTransposition": false,"secondaryFields": [],"customFields": [] }
I'm using PHP, and I've attached my sample code.
Has anyone else experienced this issue before or could one point me to the section in my code i need to fix?
Best Answer
-
Hello @judith.pillado.lseg
For some weird reason i started receiving a response. Didn't make any change on my end which is strange.
I'll keep monitoring.
Thanks
0
Answers
-
Hello,
I've noticed there is a bug on line 181 if($payload) curl_setopt($ch, CURLOPT_POSTFIELDS, $payloadJson);
It should be if($payload) curl_setopt($ch, CURLOPT_POSTFIELDS, $payload);
Correcting the above done not fix the issue.
0 -
Hello,
I've noticed there is a bug on line 181 if($payload) curl_setopt($ch, CURLOPT_POSTFIELDS, $payloadJson);
It should be if($payload) curl_setopt($ch, CURLOPT_POSTFIELDS, $payload);
Correcting the above done not fix the issue.
0 -
Hello @lazaro - thank you for reaching out to us. Unfortunately, we are unable to debug code/code for clients; however, have you tried extending the timeout exception? We always recommending waiting to throw a timeout exception between the 60 - 90 second mark. Looking forward to your response.
Judith
0 -
Hello @lazaro - thanks for the update. Let me know if there's anything else I can help you with.
Best,
Judith
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛