I am trying to run some tests with the REST API and I am running into issues. Here is my request and response:
POST https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRaw
Authorization: Token _ZMTjszC_E1-FiDGK8UsSxrNw48pQigMcHVlIbeQGf3bhN4BOgnMGcYi_ZNhGYaAvDlQiTisxA3DraV5_qVR4H5PNti1TaAGS1LVyTg9sRvVCF4xINDMgSZjgOmn-txWQwqT9g6H3cJ78cvLTMy_6MNBbvT9yRv5KjcL8jd_L5VuC2wnk45ehU5HTkD5s2v-rP5ixRXMtLvIDdTNvOImssBfyUUy8NjoxPOZySkgE6utBXF7NmC4Ybc6uY9HiAJxW2nQPOxoDb4uAbC4J7LWbIYas3bi4VEaaq-OaB9ZhAMQ
Content-Length: 0
Content-Type: application/json; odata=minimalmetadata
Prefer: respond-async
{"ExtractionRequest":{"ContentFieldNames":["Trade - Price","Trade - Volume"],"@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryTimeAndSalesExtractionRequest","Condition":{"DisplaySourceRIC":"false","QueryStartDate":"2017-01-01T09:00:00.000","ReportDateRangeType":"Range","ApplyCorrectionsAndCancellations":"true","MessageTimeStampIn":"GmtUtc","QueryEndDate":"2017-01-01T10:00:00.000"},"IdentifierList":{"":"UseUserPreferencesForValidationOptions","InstrumentIdentifiers":[],"false":null,"HASH(0x11d72030)":"ValidationOptions","@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifiersList"}}}
WARNING: Bad request for url: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRaw
400 Bad Request
{"error":{"message":"Malformed request payload: Syntax error at Line 1, Char 59: Invalid array element type for property 'ContentFieldNames'. Expected element type of 'ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionRequestBase', but found 'System.String'. {\"ExtractionRequest\":{\"ContentFieldNames\":[\"Trade - Pric"}}
I see this reported here: https://community.developers.refinitiv.com/questions/10093/dss-rest-api-error-400-malformed-request-payload.html
A JSON object is defined as a set of unordered name/value pairs. The reliance of TRTH API on ordered dictionary is a serious problem because it means you cannot use standard JSON libraries to create your requests.
This was first reported back in November. I am wondering if any progress has been made on fixing it?