Can't get Close Price from REST API
Hello. We really need your help!
We are trying to switch from the old SOAP API to the new REST API. But we encounter several problems. Here is one of them:
There are two identical requests. In one, we ask for the value of the Universal Close Price, and in the second, simply the Close Price. We get an adequate response to the first request, but the second one returns an error number 400.
Request #1:
@{"ExtractionRequest":{"@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.PriceHistoryExtractionRequest","ContentFieldNames":["Universal Close Price"],"IdentifierList":{"@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList","InstrumentIdentifiers":[{"Identifier":"MSFT.O","IdentifierType":"Ric"}],"ValidationOptions":null,"UseUserPreferencesForValidationOptions":false},"Condition":{"ReportDateRangeType":"Range","QueryStartDate":"2017-08-30T00:00:00.000Z","QueryEndDate":"2017-08-30T23:59:59.000Z"}}}
Response #1:
[{"IdentifierType":"Ric","Identifier":"MSFT.O","Universal Close Price":74.01}]
Request #2:
@{"ExtractionRequest":{"@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.PriceHistoryExtractionRequest","ContentFieldNames":["Close Price"],"IdentifierList":{"@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList","InstrumentIdentifiers":[{"Identifier":"MSFT.O","IdentifierType":"Ric"}],"ValidationOptions":null,"UseUserPreferencesForValidationOptions":false},"Condition":{"ReportDateRangeType":"Range","QueryStartDate":"2017-08-30T00:00:00.000Z","QueryEndDate":"2017-08-30T23:59:59.000Z"}}}
Response #2:
400 Bad Request
In the old SOAP API, we received the values of these fields without problems. No hints were found in the documentation. Tell me what is our mistake?
Best Answer
-
Hello @akhmed.turabov,
The template requested, PriceHistoryExtractionRequest, does not support "Close Price" as is, it supports several different Close Prices, such as " Universal Close Price" and "Official Close Price", but not "Close Price".
Different fields are available from different templates.
One way to verify if a field is supported by a template, is to request the complete list of fields that are supported by that template, with brief descriptions, with request:
{{protocol}}{{host}}{{api}}Extractions/GetValidContentFieldTypes(ReportTemplateType=ThomsonReuters.Dss.Api.Extractions.ReportTemplates.ReportTemplateTypes'PriceHistory')
It will come back with the complete list of fields such as:
...
{
"Code": "ET2.Official Bid",
"Name": "Official Bid",
"Description": "Official Bid price posted at end of pit or ring trading period.",
"FormatType": "Number",
"FieldGroup": " "
},
{
"Code": "ET2.Official Close Price",
"Name": "Official Close Price",
"Description": "The official closing price from Exchange.",
"FormatType": "Number",
"FieldGroup": " "
},
...I would suggest using free tool Postman for HTTP REST testing and our collection for Postman already has this request, step-by-step detailed explanation can be found in REST API Tutorial 4: On Demand price history extraction.
Another way is to lookup the available fields in DSS Data Content Guide.
Hope this helps
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 中文论坛