The web interface has this functionality, that I can search by Chain RIC, but I cannot find any DSS API operation that supports it.
For a deeper look into our DataScope Select REST API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials
18
●2 ●9 ●11
Do you have any information how can I search with Chain RIC with DSS API?
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query? If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
Thanks,
-AHS
Hi @lukasz.ossowski,
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If so please can you click the 'Accept' text next to the appropriate reply. This will guide all community members who have a similar question.
Thanks,
AHS
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
462
●13 ●11 ●15
Hi Lukasz,
The Chain 'search' is a little different to the other searches. My view is that this search is more of a validation check than a true search, as even for the GUI you have to know the exact match Chain RIC and it will either find (validate existence of) the specific identifier, or not...
That being the case I wonder if then the same functionality as you'd get with doing the 'search' can really just be accomplished by using the Instrument List append /validate identifier code.
Best regards,
Gareth
462
●13 ●11 ●15
var extractionsContext = new ExtractionsContext(new Uri("https://hosted.datascopeapi.reuters.com/RestApi/v1/"), "<your user id>", "<your password>");
var instrumentList = new InstrumentList { Name = "Instrument List Name" };
extractionsContext.InstrumentListOperations.Create(instrumentList);
//Append a bad identifier which will return a validation error
IEnumerable<InstrumentIdentifier> appendIdentifiers = new[] {
new InstrumentIdentifier
{
Identifier = "0#FX=",
IdentifierType = IdentifierType.ChainRic,
UserDefinedIdentifier = "Should be valid."
},
{
Identifier = "@@@",
IdentifierType = IdentifierType.ChainRic,
UserDefinedIdentifier = "Should be invalid."
}
};
var result = extractionsContext.InstrumentListOperations.AppendIdentifiers(instrumentList, appendIdentifiers, false);
//Output
foreach (var message in result.ValidationResult.Messages)
Debug.WriteLine("{0} ({1})", message.Message, message.Severity);
var createdInstrumentList = extractionsContext.InstrumentListOperations.Get(instrumentList.ListId);
extractionsContext.InstrumentListOperations.Delete(createdInstrumentList);
462
●13 ●11 ●15
HTTP/1.1 200 OK { "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ThomsonReuters.Dss.Api.Extractions.SubjectLists.InstrumentsAppendIdentifiersResult", "ValidationResult": { "ValidInstrumentCount": 1, "OpenAccessSegments": [ ], "StandardSegments": [ ], "ValidationDuplicates": [ ], "Messages": [ { "Severity": "Info", "Message": "RIC, @@@ (not found)" } ] }, "AppendResult": { "AppendedInstrumentCount": 1, "AppendDuplicates": [ ] } }
