JSON request for TRKD TimeSeries call returns 400 bad request.
Here's my JSON request, headers, and endpoint, please let me know if there is an error. Thank you.
Endpoint: (POST) http://api.trkd.thomsonreuters.com/api/TimeSeries/TimeSeries.svc
Headers:
- X-Trkd-Auth-Token : [TOKEN]
- X-Trkd-Auth-ApplicationID : [AppId]
- Accept : HTTP/1.1
- Content-Type : application/soap+xml; charset=utf-8
- Host : api.trkd.thomsonreuters.com
- Content-Length : <calculated when request is sent>
Request:
{
"GetInterdayTimeSeries_Request_5": {
"Field": [
"TIMESTAMP",
"OPEN",
"HIGH",
"LOW",
"CLOSE",
"CLOSEYIELD",
"VOLUME",
"BID",
"ASK",
"VWAP"
],
"MetaField": [
"NAME",
"QOS",
"CCY",
"TZ",
"TZOFFSET",
"NAME_LL"
],
"TrimResponse": true,
"UseNonAdjusted": true,
"NotSkipInvalidRows": true,
"Symbol": "MSFT.O",
"StartTime": "2020-07-15T10:00:00",
"EndTime": "2020-07-15T23:59:00",
"Interval": "MINUTE"
}
}
Response:
Blank, with 400 Bad Request
Best Answer
-
I used this request message:
{
"GetIntradayTimeSeries_Request_5": {
"Symbol": "TRI.N",
"StartTime": "2020-07-09T00:00:00",
"EndTime": "2020-07-16T23:59:00",
"Interval": "HOUR",
"TrimResponse": true
}
}0
Answers
-
Hi @ovx-wxu, That endpoind is for SOAP. For REST-JSON request, you need - http://api.trkd.thomsonreuters.com/api/TimeSeries/TimeSeries.svc/REST/TimeSeries_1/GetIntradayTimeSeries_5
Also, I pasted the Intraday URL, since it seems like you are requesting data for one day only.
{
'GetIntradayTimeSeries_Response_5': {
'R': [{
'C': 68.35,
'T': '2020-07-09T14:00:00+00:00'
}, {
'C': 67.17,
'T': '2020-07-09T15:00:00+00:00'
}, {
'C': 67.13,
'T': '2020-07-09T16:00:00+00:00'
}, {
'C': 67.3,
'T': '2020-07-09T17:00:00+00:00'0 -
Hello @GurpreetGurpreet. , thanks for the reply, I changed the endpoint, and now I'm getting a 500 Bad Request Error. With the following reason: "There was an error while converting from POX request. Data at the root level is invalid. Line 1, position 1."
Do you mind posting your JSON request for me to compare? Thanks!
0 -
Oh nevermind, I figured it out, I had to set the Content-Type to JSON instead of XML, it is working now. Thank you so much!
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 697 Datastream
- 1.5K DSS
- 632 Eikon COM
- 5.2K Eikon Data APIs
- 13 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 5 Trading API
- 2.9K Elektron
- 1.4K EMA
- 256 ETA
- 563 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
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 755 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
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 97 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛