I am getting this error: HTTP/1.1 400 Bad Request . Attached my complete query.

Best Answer
-
For your 2nd request:
@{"ExtractionRequest":{"@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.CorporateActionsStandardExtractionRequest","ContentFieldNames":["Corporate Actions Type","Currency Code","Fitch Issuer ID","Instrument ID","Instrument ID Type","ISIN","Issue Level Event ID","MIC","Moodys Issuer ID","OPOL","PILC","RIC","S&P Issuer ID","Security Description","Security Long Description","SEDOL","Shares Amount","Shares Amount Date","Shares Amount In Thousands","Shares Amount Type","Shares Amount Type Default Flag","Shares Amount Type Description"],"IdentifierList":{"@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList","InstrumentIdentifiers":[{"Identifier":"6758.T","identifierType":"RIC"}],"ValidationOptions":null,"UseUserPreferencesForValidationOptions":false},"Condition":{"ReportDateRangeType":"Range","QueryStartDate":"2017-05-10T16:54:22.827+08:00","QueryEndDate":"2017-05-12T16:54:22.827+08:00","IncludeInstrumentsWithNoEvents":true,"IncludeNullDates":false,"ExcludeDeletedEvents":true,"IncludeCapitalChangeEvents":true,"IncludeDividendEvents":true,"IncludeEarningsEvents":true,"IncludeMergersAndAcquisitionsEvents":true,"IncludeNominalValueEvents":true,"IncludePublicEquityOfferingsEvents":true,"IncludeSharesOutstandingEvents":true,"IncludeVotingRightsEvents":true,"CorporateActionsDividendsType":"DividendPayDate","CorporateActionsEarningsType":"PeriodEndDate","CorporateActionsStandardEventsType":"SHO","ShareAmountChoice":"All","ShareAmountTypes":[]}}}
If I run it inside Postman (a great tool for debugging) I get this error message:"Malformed request payload: For the property name \"identifierType\" in the JSON request the value could not be parsed successfully. Please check the casing or spelling of the property."
That clearly points to an issue with field identifierType. It should be IdentifierType (with a capital I).
After correction and re-run I get another error message:"Malformed request payload: Error while parsing an enum value: Requested value 'RIC' was not found."
That one comes from the IdentifierType, which should be Ric, not RIC.After correcting that 2nd error, the request runs fine.
You can use Postman in the same way to quickly debug API calls.
For your 3rd request:
@{"ExtractionRequest":{"@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryTimeAndSalesExtractionRequest","ContentFieldNames":["Trade - Price","Trade - Volume","Trade - Exchange Time"],"IdentifierList":{"@odata.type":"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList","InstrumentIdentifiers":[{"Identifier":"6758.T","identifierType":"RIC"}],"ValidationOptions":null,"UseUserPreferencesForValidationOptions":false},"Condition":{"MessageTimeStampIn":"GmtUtc","ApplyCorrectionsAndCancellations":true,"ReportDateRangeType":"Range","QueryStartDate":"2017-05-10T16:55:13.288+08:00","QueryEndDate":"2017-05-12T16:55:13.288+08:00","DisplaySourceRIC":true}}}
It has exactly the same 2 errors.
For your 1st request:
@{"Request":{"IdentifierList":"{\"@odata.type\":\"#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList\",\"InstrumentIdentifiers\":[{\"Identifier\":\"XS062249170\",\"identifierType\":\"ISIN\"}],\"Range\":\"{\\\"Start\\\":\\\"2017-05-08T00:00:00.000Z\\\",\\\"End\\\":\\\"2017-05-11T00:00:00.000Z\\\"}\"}"}}
I'm still trying to guess what this one is for (hence my request for the method and endpoint URL). That said, I see the same error on the syntax of IdentifierType, and you should replace ISIN with Isin. That should help.
0
Answers
-
400-bad-request.txt @Christiaan Meihsl
0 -
Could you please also tell us what method you are using (GET, POST) and what endpoint URL you are using, for each of these 3 requests ? It is difficult for us to guess what you are tying to achieve, especially for the first one.
0 -
I guessed the 2nd and 3rd, and found 2 errors in the 1st query, but could not test the 1st because I don't know what endpoint you are using. If my answer below does not suffice, please communicate the endpoint you are using.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 250 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛