Tick History Cash Quota Limit
I am getting the following message as output from my Elektron request. However, in the screenshot below, I am below my listed quotas? What is the cash quota, and why is it limiting the requests?
This is a relevant post about the same issue. https://community.developers.refinitiv.com/questions/68915/tick-history-cash-quota-exceeded.html
Quota Message: INFO: Tick History Cash Quota Count Before Extraction: 0; Instruments Approved for Extraction: 0; Tick History Cash Quota Count After Extraction: 0, 100% of Limit; Tick History Cash Quota Limit: 0
Quota Message: ERROR: The RIC 'S420F1' in the request would exceed your quota limits. Adjust your input list to continue.
Best Answer
-
Hello @nathan.faber,
I just run the same request, the result for me seems to be the same as yours- not all fields requested are populated for every instrument.
This developers forum can be of most use to you with questions and discussions centered around Refinitiv API usage, the majority of the forum members are developers working with Refinitiv APIs, the moderators of the forums are Refinitiv API experts.
For questions on content, for example, what fields for specific instrument type carry the content that you require, what content is available/not available, the best and most efficient way for a customer to get these answered by Refinitiv content experts, is by submitting them to Refinitiv Helpdesk Online -> Content -> Tick History .
Let us know if you will be able to proceed, or like us to help by submitting on your behalf?
0
Answers
-
Hello @nathan.faber,
There are two issues that can be pertaining:
First, it may be worthwhile to confirm if you are permissioned for the instrument requested, S420F1 , it may be that you are not permissioned for the instrument type, and your quota for the type is 0, any request for that instrument would take you over Quota limit. I would suggest to get in touch with your Refinitiv account team, to confirm what instrument set(s) your organization has contracted and your id is permissioned for.
When one is permissioned, the instrument that requested, S420F1, is not currently valid, it is expired.
For example, if I request ElektronTimeSeries this way:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ElektronTimeseriesExtractionRequest",
"ContentFieldNames": [ "RIC", "Ask", "Bid", "Trade Date" ],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{ "Identifier": "S420F1", "IdentifierType": "Ric" }
]
},
"Condition": {
"ReportDateRangeType": "Range",
"QueryStartDate": "2015-12-01T00:00:00.000Z",
"QueryEndDate": "2022-12-02T00:00:00.000Z"
}
}
}The result is
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionResult",
"Contents": [
{
"IdentifierType": "Ric",
"Identifier": "S420F1",
"Error": "Not found"
}
],
"Notes": [
"All identifiers were invalid. No extraction performed."
]
}If I include allowing for instruments that are historic, not valid anymore:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ElektronTimeseriesExtractionRequest",
"ContentFieldNames": [ "RIC", "Ask", "Bid", "Trade Date" ],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"ValidationOptions": {
"AllowHistoricalInstruments": true
},
"UseUserPreferencesForValidationOptions": false,
"InstrumentIdentifiers": [
{ "Identifier": "S420F1", "IdentifierType": "Ric" }
]
},
"Condition": {
"ReportDateRangeType": "Range",
"QueryStartDate": "2015-12-01T00:00:00.000Z",
"QueryEndDate": "2022-12-02T00:00:00.000Z"
}
}
}We see non-empty historic results, please note, one has to be permissioned for the content.
Hope this information helps
0 -
As I showed in the screenshot, I am permissioned for 30 options chains and I have only used 6. I am using a request like your second one and also having other issues. For example, in the request below, I only get futures data back and all the options are blank.
'{"ExtractionRequest": {"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.ElektronTimeseriesExtractionRequest", "ContentFieldNames": ["RIC", "Trade Date", "Settlement Price", "Low", "High", "Open", "VWAP"], "IdentifierList": {"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList", "InstrumentIdentifiers": [{"Identifier": "0#C+", "IdentifierType": "ChainRIC"}], "ValidationOptions": {"AllowHistoricalInstruments": true, "AllowInactiveInstruments": true}, "UseUserPreferencesForValidationOptions": false}, "Condition": {"ReportDateRangeType": "Range", "QueryStartDate": "2016-01-01", "QueryEndDate": "2016-07-01"}}}'
0 -
Yes, please submit on my behalf. Thanks!
0 -
Hello @nathan.faber ,
Support case #10100898 was opened on your behalf, please expect us to reach out to you via email.
0 -
Hello @nathan.faber
The TRTH support team suggest the following resolution via the case #10100898
With regards to your query, I confirm that the corn options chain RIC is <0#1C+> for the year 2016. Hence please use this chain RIC to pull the Elektron timeseries data.
I have crossed checked the data and confirm we have valid updates.
Effective from the 1st of June 2014, The RIC structure for the CBT exchange content (Futures, Spreads, Options) was changed. Please find the below DN for details regarding the RIC root changes.
https://my.refinitiv.com/content/mytr/en/datanotification/DN070606.html
Kindly let me know if you have any additional questions.0
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 中文论坛