What is difference between World-Check One API v1 and World-Check One API V2?

What is difference between World-Check One API v1 and World-Check One API V2?
Best Answer
-
You can switch from v1 to v2. Only the url changes from v1 to v2 ( in each section of the Authorisation format ). Since v2 is the current version we would recommend you to try out the v2 version in the pilot environment
Version v2 has all the capabilities of v1 plus below capabilities -
- Bulk Screening ( Asynchronous ) - ( up to 50 cases be created using 1 API call )
- Bulk retrieve screening status - ( Screening status of up to 50 cases can be retrieved using 1 API call )
- Sync screening - (Returns the caseSystemId in response along with results)
- Link / Unlink cases ( link/unlink cases to each other )
- User Activity monitoring
- Retrieve MRZ lines (Passport check)
- Media-Check screening
- Media Check results
- Media Check articles - ( Attach / Remove )
You may download the collection and the environment from the following link - "https://developers.refinitiv.com/en/api-catalog/customer-and-third-party-screening/world-check-one-api/documentation" .
Hope this helps.
0
Answers
-
Thanks for your query.
V1 is the older version of the API and v2 is the latest version of the API. The v2 version has more capabilities including Media-Check screening via the API.
Can you please let us know what specific information is needed regarding v2?
0 -
We are currently on V1 version on production as well as on pilot environment.
We are planning to change WC API url from in-premises URL to AWS URL for production environment.
Wanted to know if we need to move to v2 version or we should stay on v1 version?
If we have to change from v1 to v2 then what are the thing we should take care?
What are the advantages of V2?
0 -
If we do not want any new functionalities of v2 version and still if we switch to v2 version on production then will it have any impact?
0 -
Can you please provide us the workflow of your API calls or the endpoint which you are using at the moment?
0 -
Please let us know if below endpoints will have any impact due to version change from v1 to v2.
SEQ-case-investigate-results: Get screening resultsSEQ-screen-async: Screen a caseSEQ-case-investigate-results: Get screening resultsSEQ-case-audit: Retrieve the audit log for a caseSEQ-case-update: Update a caseSEQ-screen-sync-organisation: Perform Synchronous Screening: OrganisationSEQ-screen-sync-individual: Perform Synchronous Screening: IndividualSEQ-case-retrieve: Get the system ID of a caseSEQ-case-ogs-enable: Enable ongoing screening for a case0 -
Based on the below details provided in the dev portal, there would not be any impact on the integration.
SEQ-case-investigate-results: Get screening results
SEQ-screen-async: Screen a case
SEQ-case-investigate-results: Get screening results
SEQ-case-audit: Retrieve the audit log for a case
SEQ-case-update: Update a case
SEQ-screen-sync-organisation: Perform Synchronous Screening: Organisation
SEQ-screen-sync-individual: Perform Synchronous Screening: Individual
SEQ-case-retrieve: Get the system ID of a case
SEQ-case-ogs-enable: Enable ongoing screening for a caseHowever, in v2 Sync screening approach, the caseSystemId is returned in the response itself, so you can eliminate the additional API call – ‘SEQ-case-retrieve: Get the system ID of a case’. Using this approach would be more effective, as it eliminates the use of an additional API call.
You may test and try it out in the pilot environment.
0 -
We would like to know if we can stay on v1 version even after moving to worldcheck AWS API url.
Is there any expiry date for v1 version or it will be supported further?
I can see there is difference in JSON response in v1 vs v2 version for "SEQ-case-update: Update a case". We are getting error while parsing response as there is difference in v1 and v2 version.
Below is one of difference.
V1 version
"caseScreeningState":"INITIAL"
V2 version
"caseScreeningState":{"WATCHLIST":"INITIAL"}
0 -
v1 would be supported on AWS.
The JSON object which you are referring to are optional and v2 contains more fields in the response. The existing fields of v1 would still work.
0
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
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 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
- 275 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
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛