What are the guidelines for high volume testing of the World Check One API in Pilot environment?

We are planning to do high volume testing of the World Check One API in the Pilot/Test environment. The plan is to send a total of approx. 10,000 individuals, companies and vessels.
For each of the 10,000 records, we will check to see if a Case ID exists, and if not create one, and then send a request for ongoing screening.
1. Should there be a delay between the calls for each record, and if yes, how many seconds?
2. Can you provide at least a rough estimate for the total duration of the processing of the 10,000 cases?
Best Answer
-
Hi,
So if I understand correctly the total testing volumes are 10000 API calls, what we usually recommended our clients with respect to the traffic/second is 5 API calls/second, but they can consume more calls but it depends on few factors like:
- The names being screened: If you screen a common name like Muhammed/John smith, the amount of time taken for the service to come back with a response is fairly high as the call would fetch large amounts of data from the database.
- The number of hops between your systems and the server.
- Platform availability at that moment.
So we encourage our clients to perform adequate testing to see how the platform behaves with the kind of data and traffic volumes being tested.
To answer your queries:
1. Should there be a delay between the calls for each record, and if yes, how many seconds?
- As mentioned above, you can send up to 5 API calls/Second and they would go through easily, you can make more than 5 but then you may get a 429 response code and its probability depends on the above-mentioned reasons, if you would like a smooth transitions of requests and have no constraints with a buffer between API calls then you may try to give a buffer of 1 second between each call and see how the tests results pan out.
2. Can you provide at least a rough estimate for the total duration of the processing of the 10,000 cases?
- Unfortunately, we cannot provide this information, you will have to perform the relevant tests and derived the respective results.
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
- 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
- 716 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 中文论坛