BondScheduleExtractionRequest CALL
hi,
I'm looking for the syntax to get detail fro a call.
With the syntax here after i don't get information
Could you please help.
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.BondScheduleExtractionRequest",
"ContentFieldNames": [
"Call Begin Notify Period",
"Call Final Price",
"Call Refund Limit Rate",
"Call End Date",
"Call End Notify Period",
"Call Frequency Description",
"Call Effective Date"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [ { "Identifier": "XS1746116299", "IdentifierType": "Isin" } ],
"ValidationOptions": {
"AllowOpenAccessInstruments": true,
"AllowHistoricalInstruments": true,
"AllowLimitedTermInstruments": true,
"AllowInactiveInstruments": true,
"AllowUnsupportedInstruments": true,
"ExcludeFinrAsPricingSourceForBonds": true,
"UseExchangeCodeInsteadOfLipper": true,
"UseUsQuoteInsteadOfCanadian": true,
"UseConsolidatedQuoteSourceForUsa": true,
"UseConsolidatedQuoteSourceForCanada": true,
"UseDebtOverEquity": true,
"UseOtcPqSource": true,
"AllowSubclassImport": true
}
},
"Condition": { "BondScheduleTypeCodes": [ "CALL" ] }
}
}
Best Answer
I have just run a request with your query, and receive data:
{
"IdentifierType": "Isin",
"Identifier": "XS1746116299",
"Call Begin Notify Period": 60,
"Call Final Price": 100,
"Call Refund Limit Rate": null,
"Call End Date": "2019-12-10",
"Call End Notify Period": 30,
"Call Frequency Description": "One time",
"Call Effective Date": "2019-12-10"
}
The query syntax is therefore correct, and data is available.
If you are not receiving data, there might be a permissioning issue. Can you please run the request using the ExtractWithNotes end point, and post the extraction notes ? They should help us understand what is happening.
@christiaan_meihsl
Many thank for your answer. My http was not correct it was "RawExtractionResults" instead of "/Extractions/ExtractWithNotes"
Now it works fine.
Regards
@olivier.dauba, glad you found the root cause of the issue. Have a great day.