Limits on EquitySearchRequest
Hi - I wanted to confirm, does DataScope.Select.Api.Search.EquitySearchRequest have any quota or limits associated with it? I would like to call it for several hundred ISINs using the REST API, and want to make sure that we won't incur any charges or go against any limits for this.
Also, in the new site structure, I couldn't seem to find any documentation about this API. Can someone point me to it and also a link to the best practices document for it, if there is one?
Thanks,
Wayne
Best Answer
-
@waynes ,
This is correct, doing search by ISIN first will not count toward quota, and therefore will not affect your bill.
0
Answers
-
Hi @waynes ,
You are correct, search requests do not count toward your user quota.
DSS documentation:
- Refinitiv DataScope Select - REST API Documentation
- DataScope Select Best Practices & Fair Usage Policy
- Just in case: Extraction Limits by Report Template
0 -
Thanks for the quick reply. On this doc you sent: https://developers.refinitiv.com/content/dam/devportal/api-families/datascope-select/datascope-select-rest-api/documentation/overview-and-concepts/ds_th_best_practices_and_fair_usage_policy_apr2021.pdf
On page 17, it looks like it says for Search, there is "Maximum Requests" and it says 1500. I assume that means within the 60 sec timeout period?
Also, aside from the technical limits, would we get billed in some way for the data returned by using EquitySearch? I'm not clear how this API fits in with the other APIs which trigger extractions, etc. I know report templates get tracked and billed for Tnc, pricing, etc. Is the search API via REST a totally different thing?
Thanks,
Wayne
0 -
Hi @waynes ,
You are correct, recommended max search requests per 60 seconds is 30 and maximum requests per 60 seconds is 1500.
The search request itself does not count toward user quota. Usually, having identified the required content via search, one would next request extraction of the required instruments, that would be applicable toward user quota.
0 -
Thanks again - but just to be specific - when you say it doesn't count towards quota, does this also mean we are not billed for those requests?
The use case you described is what we plan to do - first a fetch using the EquitySearch API by ISIN, which returns all the RICs, and then an extraction on just the RICs we care about. Just want to confirm that doing the request by ISIN first is not going to blow up our bill or somehow affect our account.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 48 Data Fusion
- 34 Data Model Discovery
- 694 Datastream
- 1.5K DSS
- 630 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 561 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
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 732 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
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛