DELTA_SYNC vs FULL_SYNC in Screening Requests
I am expecting that the results obtained by using screeningMode=DELTA_SYNC
with the /cases/{caseSystemId}/screeningRequest
endpoint accumulate from the initial screening. However, are these results actually just the differences from the most recent screening? Also, I understand that by requesting with FULL_SYNC
, all results can be obtained. If there are any issues or misunderstandings regarding this, could you please clarify?
Best Answer
-
Hi @satom ,
Thanks for reaching out to us!
DELTA_SYNC: Delta Screening performs Screening from the time of the last screening date and shows new results that appeared after the last screening, if there are not new results the results array will be empty.
FULL_SYNC: When you perform FULL_SYNC it does the full rescreening as similar to the initial screening and gives all the results (matched records) for the entity which you have screened.
Please access our latest API documentation to find more details about the same LSEG World-Check One API.
Thanks
Sai
0
Answers
-
Hi @anisetti.saikiranreddy01 ,
Thanks for your prompt response.
I got it! But I have aditional questions.- Does The last screening include On-Going-screening?
- Is the cost the same for using DELTA_SYNC as it is for FULL_SYNC?
Thanks
Satom0 -
Hi @satom,
Please find my comments below.
- On-going screening will not automatically be enabled during your initial screening process, it is that you need to enable it during your initial screening stage or even later depending on your requirement, in order to enable OGS during your initial screening you just need to change the caseScreeningState of WATCHLIST to ONGOING in your request body while screening an entity "caseScreeningState": {"WATCHLIST": "ONGOING"}
- There will not be any extra cost for DELTA_SYNC or FULL_SYNC as this you are just re-screening an existing case for updated results and it's not that you are creating/screening a new case.
1
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 中文论坛