The matches returned from api are different from matches shown on the web application

I was using the following request SEQ-2f, 4a, 8, 5b to retrieve the results for the keyword "CHINA":
{
"groupId":"{{group-id}}",
"entityType":"UNSPECIFIED",
"providerTypes":[
"WATCHLIST"
],
"name":"CHINA",
"customFields":[
]
}
and 7 matched results was returned. (using the production api)
However, if I enter the same keyword "China" and select "UNSPECIFIED" to search on the web application, then 8 results will be returned.
May I know the reason and how we could resolve it? Thank you.
Best Answer
-
In order to check the group using the API, you can use the API call - 'SEQ-case-investigate-case-details: Fetch full case details'.
For the UI, you can use the case-Id and filter the search using the group in the case manager.
In order to check the Ids of all the groups, you can use the API call - 'SEQ-pre-groups: Get my top-level groups'
Also, for the issues related in production, you may refer to this link going forward. I will get a support ticket raised for this issue on your behalf and we can continue to look into it.
0
Answers
-
Thank you for your query.
That's strange! Can you please share the result details from the UI and the API to look into it?
0 -
0
-
0
-
Please find the body contents as follows
(SEQ-2f):{
"groupId":"{{group-id}}",
"entityType":"UNSPECIFIED",
"providerTypes":[
"WATCHLIST"
],
"name":"CHINA",
"customFields":[
]
}Thanks.
0 -
Thank you for sharing the details.
Can you please confirm if both the cases are created using the same group or different groups?
Also can you please confirm if you are using the pilot environment or the production environment for the above case?
0 -
The issue occurred in the production environment.
About the group, how could I confirm the groups used in API and UI are the same?
0 -
I have a question talk about
the request word check API method invoke
order.I will get "matchStrngth" key from result values.
This request API invoke order is
- SEQ-pre-groups: Get my
top-level groups - SEQ-case-create-individual:
Save a case: Individual - SEQ-case-retrieve: Get the
system ID of a case - SEQ-case-ogs-enable: Enable
ongoing screening for a case
Is the above correct?
0 - SEQ-pre-groups: Get my
-
I would suggest posting the second query as a separate question, not as an answer to the first one.
Once an answer is accepted, marked as "correct", the community tends to only look at the accepted answer, and may miss your second question on the same topic. If required you can always refer to the original question by adding a link to it.
Kind regards, AHS0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 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
- 559 WebSocket API
- 39 FX Venues
- 15 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
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 717 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛