HTtp request throwing error.

gkusampudi

I am trying the following code on postman with token and I got the following response

{

"error": {

"message": "The Authorization header is malformed. Supported Authorization types are Token,Basic."

}

for the below request

Content-Type: application/json; odata=minimalmetadata

{

"ExtractionRequest": {

"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.ElektronTimeseriesExtractionRequest",

"ContentFieldNames": [

"Ask",

"Bid",

"High",

"Last",

"Low",

"Trade Date"

],

"IdentifierList": {

"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",

"InstrumentIdentifiers": [

{

"Identifier": "TRI.N",

"IdentifierType": "Ric"

}

],

"ValidationOptions": null,

"UseUserPreferencesForValidationOptions": false

},

"Condition": {

"ReportDateRangeType": "Range",

"QueryStartDate": "2015-12-01T00:00:00.000Z",

"QueryEndDate": "2015-12-02T00:00:00.000Z"

}

Find more posts tagged with

dss-rest-api

tick-history-rest-api

Accepted answers

zoya faberov

Hello @gkusampudi ,

I was able to run the same request via Postman, without issues. I have updated the headers to include Content-Type: application/json and odata=minimalmetadata.

From the error message, it appears that a wrong Authorization type is applied.

As the issue does not appear to be with the request or the headers as listed but with the authorization, suggest to work through tutorial REST API Tutorial 7: On Demand End of Day extraction by downloading Postman starter and submitting the included naked ElektronTimeseries request via Postman. If that works as expected, update request body to your request. if that also works as expected, the next step is to verify Authorization aspect in your custom code.

Please see that the tutorial collection uses "Inherit Auth from parent" type of Authorization, which is populated with "No Auth", and passes Authorization token in Headers. if I change Authorization type to "Bearer Token" I am able to reproduce the same error as you see. Therefore, believe the aspect to verify in the code should be Authorization, and it should emulate the working approach from tutorial.

Hope that this information is of help

All comments

zoya faberov

Hello @gkusampudi ,

I was able to run the same request via Postman, without issues. I have updated the headers to include Content-Type: application/json and odata=minimalmetadata.

From the error message, it appears that a wrong Authorization type is applied.

Hope that this information is of help

gkusampudi

refinitiv.pdf. I have attached Header, Body and Authorization screenshots from postman. can you point out where is it wrong?

refinitiv.pdf

Jirapongse

@gkusampudi

The token must be prefixed with Token.

gkusampudi

I tried with Token{_0l86oyVJn...}

got the following error

{

"error": {

"message": "Authentication request failed because of invalid token"

}

I have pulled the above token using this

{

"Credentials": {

"Username": "XXXXX",

"Password": "XXXXX"

}

Jirapongse

It should be:

Token _0l86oy...

I removed the token.

gkusampudi

now getting permission error.

1668659722441.png

gkusampudi

now getting permission error.

Jirapongse

@gkusampudi

Please contact your Refinitiv account team or Sales team directly to verify your permission. The ElektonTimeSeriesReportTemplate is for the Tick History product.

If you don't have permission to access the Tick History product, you can't use that template.

Please refer to the DataScope Select Tutorials for the sample DSS requests.

EXPLORE OUR SITES