Request 1:

{  "SearchRequest": {    "InstrumentTypeGroups": [      "Equities"    ],    "IdentifierType": "OrgId",    "Identifier": "120106760,120107693,120088642,120113117,120149723",  "PreferredIdentifierType": "Isin"  }}

Request 2: {  "SearchRequest": {  "InstrumentTypeGroups": [      "Equities"    ],    "IdentifierType": "OrgId",    "Identifier": "120088642,120106760,120107693,120113117,120149723",  "PreferredIdentifierType": "Isin"  }}

Regards, Imran

Example RICs : ZARQB3J4Y, ZAR18X21F

For the new broker requirement, we need broker/contributor-level fields (e.g., contributor RIC, contributor name, bid/ask per contributor , Ask Clean Price, Bid Clean Price, Coupon Rate, Currency Code, ISIN, Issuer Name, Maturity Date, Mid Clean Price, RIC, Trade Date, Unchanged - Report Date.)

For our existing DataScope Select calls:

Auth: POST https://selectapi.datascope.lseg.com/RestApi/v1/Authentication/RequestToken

Extraction: POST https://selectapi.datascope.lseg.com/RestApi/v1/Extractions/ExtractWithNotes

Data type used: EndOfDayPricingExtractionRequest / PriceHistoryExtractionRequest

For the new broker requirement, we would appreciate guidance on the correct endpoint to retrieve all broker contributors for a list of ~5,000 RICs in bulk

• When we run certain set of instruments during the market close which contains both embargoed and non embargoed data, What would be the output ? 
  
  - Will i get only non embargoed data even though i don't provide the user validation as "OnlyNonEmbargoedData": true" Or will i get embargoed and Non Embargoed data once the embargo is lifted ?                                                                                       

OR

• Should i have to specify the user validation as "OnlyNonEmbargoedData": true" to get the only the non embargoed data.

I'm trying to replicate the DSS GUI behaviour when it comes to chain expansion.
i.e. go to Chains Search, then click Search:

And then click on the chain itself to see:

And so on…

Endpoint https://selectapi.datascope.lseg.com/RestApi/v1/Search/HistoricalChainResolution only works with a Tick History account. I'm using a DSS account. What's the alternative?

I've tried endpoint https://selectapi.datascope.lseg.com/RestApi/v1//Extractions/InstrumentListValidateIdentifiersbut it only validates that the the chain exists, not the chain constituents.

Do I have to extract the data through one of the templates instead?

Thanks in advance for your views.

Is it possible to adjust the body of the request provided in the tutorial to get data aggregated to 1min?

If so - can you please explain how to do this?

What I would like to be able to do is to get EUR= fx OHLC data aggregated at 1min frequency.

CorporateActionsIsoExtractionRequest (Equity)
DebtCorporateActionsIsoExtractionRequest (Debt)

Observed Issues
1)Older SWIFT Messages Returned Instead of Latest Only
We observe that the API returns:
Multiple historical SWIFT messages (MT564 / MT568)- Includes older versions, updates, and prior notifications
:98C::PREP//20260224171541 --> the date here is 24-Feb-2026

2)Expired / Completed Events Still Included
We are receiving SWIFT messages for:
Events past expiration date
Events past election deadline
We must need below two tags in every swift messages-
:98E::EXPI//20250619160000/0100
:98E::MKDT//20250619160000/0100
and also the MKDT and EXPI should be greater than or equal to todays date.
I can see lot of messages with no above tags.

1. MT568 messages sometimes appear before MT564
   Ideally it should be MT564 swift message first and then MT568. How it can be done?

Queries for LSEG
Q1. How can we retrieve only the latest SWIFT message per event?
Is there a parameter or configuration to:
return only the latest revision per corporate action (SEME/CORP)?
exclude older / superseded / canceled messages?

Q2. How can we filter out expired / completed corporate action events?
Is there a way to exclude:
expired events
past election deadlines
completed / settled events

Q3. Is there any way to enforce ordering of SWIFT message sequence?
MT564 first
followed by MT568

For equity -
API details -
https://selectapi.datascope.lseg.com/RestApi/v1/Extractions/ExtractRaw
Body -
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.CorporateActionsIsoExtractionRequest",
"Condition": {
"ReportDateRangeType": "Init",
"ReportIsoEvents": [
"BIDS",
"TEND",
"EXRI",
"PRIO",
"CONV",
"EXOF",
"MRGR"
],
"IncludeNonPendingEvents": true,
"GrossAmountOnlyForPaymentEvents": true,
"ExcludeNilPaidFromPaymentEvents": true,
"IncludeCusipCinsIn35B": true,
"Wrap35BLines": true
},
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "CA01921D2041",
"IdentifierType": "Isin",
"Source": "*"
}
],
"ValidationOptions": {
"AllowOpenAccessInstruments": true,
"AllowHistoricalInstruments": true,
"AllowInactiveInstruments": false
},
"UseUserPreferencesForValidationOptions": false
}
}
}

For Debt -
API BODY -
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.DebtCorporateActionsIsoExtractionRequest",
"Condition": {
"ReportDateRangeType": "Init",
"IncludeInstrumentsWithNoEvents": true,
"IncludeNullDates": true,
"ExcludeDeletedEvents": true,
"IncludeNonPendingEvents": true,
"ReportIsoEvents": [
"BIDS",
"DTCH",
"TEND",
"CONS",
"BPUT",
"CONV",
"EXOF"
],
"IncludeCusipCinsIn35B": true,
"Wrap35BLines": true
},
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "CA01921D2041",
"IdentifierType": "Isin",
"Source": "*"
}
],
"ValidationOptions": {
"AllowOpenAccessInstruments": true,
"AllowHistoricalInstruments": true,
"AllowInactiveInstruments": false
},
"UseUserPreferencesForValidationOptions": false
}
}
}

  ],
  "StandardSegments":[
     {
        "Code":"U",
        "Description":"Muni",
        "Count":1
     }
  ],
  "ValidationDuplicates":[
     
  ],
  "Messages":[
     
  ]

}
}

3. Take the ValidatedInstrument and append to list
{
"ValidatedInstruments": [
{
"Identifier": "US625517PM31",
"IdentifierType": "Isin",
"UserDefinedIdentifier": "US625517PM31",
"Source": "EJV",
"Key": "VjF8MHgwMDEwNmFhNWI0ZWMwNTgyfDB4MDAxMDZhZGViOGVjMDVmNXxFSlZ8TVVRUnxNVU5JfE1VTkl8VXxOfDYyNTUxN1BNMz1SUlBTfE1VTkk",
"Description": "OR 5.000 06/15/28",
"InstrumentType": "MortAggregate",
"Status": "Valid"
}
],
"KeepDuplicates": false
}



4. Here we get a 403 FORBIDDEN response.

Please note, this works for 99% of validated instruments. However there are a few which cause this 403 response. ISIN US68609UPA78 is another example.

Can you explain why the AppendToList fails with Validated Instruments for a very small amount of ISIN?

I require your assistance in how to link a Report template from DSS Web GUI to my API Body.

My DSS ID is 9030150, and for example I want to link the Report that is saved as EOD Pricing in my Report Templates. How do I build my API?

Also, can I build this API by only selecting Report template from Web GUI and not the instrument list. And can this be an OnDemand extraction or does it need to be a scheduled extraction only.

Thank you for your assistance.

Regards,

Anirudh

While we can successfully delete a single Instrument List by supplying its ID, the bulk‑delete operation returns a 404 error when we invoke the endpoint.

Could you please advise on the correct usage of InstrumentListDeleteMultiple or any additional parameters that may be required to perform a successful batch deletion?

Thank you in advance for your assistance.

(2) Re Timezone settings for scheduled extraction, I am checking below microsoft timezone index for DSS timezone. If we would like to select British Standard Time (not fixed GMT/UTC, but timezone with1 hour difference summer and winter time), shall we select "GMT Standard Time - Greenwich Mean Time: Dublin, Edinburgh, Lisbon, London)"?

Microsoft Time Zone Index Values | Microsoft Learn

Regards,

Hiroko

If clients need to post request at a certain time out side of DSS REST API funciton, please advise accordingly.

Regards,

Hiroko

Want to know how to pass multiple "ReportIsoEvents" under "@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.DebtCorporateActionsIsoExtractionRequest"and"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.CorporateActionsIsoExtractionRequest"Suppose I have below events - "BIDS", "DTCH", "TEND", "CONS", "BPUT", "CONV", "EXOF"How to pass them in request body?

Let me attach DSS GUI image which I am looking for.

Regards,

Hiroko

(1) Is it correct to assume that values other than numbers are enclosed in double quotes ("")?

(2) If the value is empty, are numbers are null (or null codes for EoD/Elektron EoD/Price History) and other types enclosed in double quotes (""")?

Regards,

Hiroko

I tried to look at the existing sample script <dss-python-shareholder-rights-sample> .. but it looks quite complex.

Appreciate your help.

I input filecode 2 in API instrument identifier as below.

{"Identifier": "2", "IdentifierType": "FileCode" },

Shall I just wait to retrieve pricing data or am I missing something?

Regards,

Hiroko

Client usage:

- Multiple application instances share a single DSS user account.

- Each instance executes the PriceHistoryExtractionRequest on demand via ExtractWithNotes.

- During peak periods, approximately 10-40 extraction requests are sent simultaneously.

1. Regarding the limit on concurrent extraction processing: The Best Practices document (ver. 9.2) states that the "Concurrent extraction processing limit is 2 per report template per user." Does this limit also apply to PriceHistoryExtractionRequests? Specifically, if 10 PriceHistoryExtractionRequests are submitted simultaneously from the same user account, will only 2 be processed and the rest be queued?

2. Regarding queue behavior: Are requests that exceed the concurrent processing limit automatically queued? Is there a maximum queue size or timeout?

3. Regarding the rate limit for on-demand extraction: Is the Fair Usage Limit (30 on-demand extraction requests/60 seconds) mentioned in the documentation a per-user limit? Am I correct in understanding that HTTP 429 is returned when the limit is exceeded?

4. Regarding recommended configuration: In our use case (extracting multiple time-series stock price data for different stocks in parallel), please let us know if there is a recommended approach to maximize throughput within the fair usage range.

5. Regarding limit increases: Is it possible to increase the limit of concurrent extraction processes for this client’s account?

Regards,

Hiroko

Client comments:

The idea is to integrate this in our cost calculation application. I’ve been experimenting with this and am able to get results via DataScope.Select.Api.Search.FuturesAndOptionsSearchRequest.

It does however seem important to run the search requests for a specific exchange code. Searching on ALL is just too time-consuming or even timeouts.

What I’m now looking for is a way to programmatically retrieve this list of exchange codes (from the DSS api?) in order to offer it on our search screen.

Could you please check with your tech colleagues or maybe point me to some online LSEG article that explains how to do this.

Can you please help me with supporting documentation for the client?

In the DSS GUI, we were able to change the decimal places for each field, and was able to get the exact prices. For their production, they need to go through the API.

My questions are:

1. In the API script, can you include decimal preferences for each field?

2. If not, if the report template has the necessary changes to the fields, can the API run that report template ID? IF so, what would be the header and script?

"ReturnLastTradingDayPriceOnNonTradingDay": true,

      "ReturnNullCodeValuesInExtractionPricingFields": false

I received below error message.

Would you advise what is the wrong with this?

• Error Message

400 bad request

 "error": {

        "message": "Malformed request payload: For the property name \"ReturnLastTradingDayPriceOnNonTradingDay\" in the JSON request the value could not be parsed successfully. Please check the casing or spelling of the property."

• Request:

{

  "ExtractionRequest": {

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

  "ContentFieldNames": [

  "ISIN",

  "Issuer Name",

  "Trade Date",

  "Universal Close Price",    

  "Volume"

  ],

  "IdentifierList": {

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

  "InstrumentIdentifiers": [

  { "Identifier": "US5949181045", "IdentifierType": "Isin" },

  { "Identifier": "IBM.N", "IdentifierType": "Ric" }

  ]

   },

    "Condition": {

      "ReturnLastTradingDayPriceOnNonTradingDay": true,

      "ReturnNullCodeValuesInExtractionPricingFields": false

    }

  }

Regards,

Hiroko

They would like to migrate from the current API "RFA Java 7.6 + Marketfeed format" to the DSS REST API as easily as possible.

With RFA Java 7.6 + Marketfeed format, RIC and fields were set in Java XML format, so They wanted to understand how it would work in Java.

Please find the following 3 questions:

1. If they are going to use Java, they would need to use separate programming because they wouldn't be using the SDK, so is it correct to assume that this would make the migration more time-consuming?

2. They understand that using the SDK makes the migration easier. Please advise if this understanding is correct.

3. They understand that the SDK will be written in C#, and would like to know how will the RIC and fields be configured? Currently, the data is acquired in the attached XML file format (converted to text file to attach) , so I would appreciate it if you could check this.

1. Javaを利用しようとする場合、SDKを使用しないため別途プログラミングが必要となり、より移行に手間がかかる認識でよいでしょうか。
2. SDKを使用したほうが簡単に移行できるものと理解しておりますが齟齬あればご指摘いただきたいと思います。
3. SDKの場合、C#の言語となると理解しておりますが、RICや取得項目の設定はどのようになるでしょうか。現在は添付のxmlファイルのような形式で取得しておりますので、ご確認いただけますと幸いです。

(1) Is this paramter related to only DSS preferences for "instrument validations" such as

"Exclude FINR as Pricing Source for Bonds", "Use Exchange Code Instead of Lipper as Mutual Fund Default Source" etc.?

(2) I have a client who is interested in DSS preference "Exclude Null Codes For Universal Close Price". Can we still use REST API paramter "UseUserPreferencesForValidationOptions" for this preference option? I mean, if we select "true" for above parameter, Does DSS REST API choose settings from GUI preferences?

while trying new DNS as per "PCN215272-DataScope Select & Tick History API Access Changes Requiring Client Action", we get erro 502 "Bad Gateway". What is the meaning of this?

The Call is structured as follow:

1. Sending a PUT request to: https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ReportTemplates(‘template_id’)
2. Using the following json body:

• {

• "@odata .type":"#DataScope.Select.Api.Extractions.ReportTemplates.PriceHistoryReportTemplate",

• "ReportTemplateId":"template_id",

• "ShowColumnHeaders":false,

• "CompressionType":"None",

• "Name":"fake_template",

• "OutputFormat":"CommaSeparatedValues",

• "ReportFieldCount":4,

• "Delimiter":"None",

• "DeliveryType":"None",

• "Destination":"",

• "TemplateTypeCode":"ET2",

• "Headers":[

• ],

• "Trailers":[

• ],

• "ContentFields":[

• {

• "FieldName":"ISIN",

• "Justification":"Left",

• "Label":" ",

• "Width":-1,

• "WidthStyle":"VariableWidth",

• "Format":{

• "@odata .type":"#DataScope.Select.Api.Extractions.ReportTemplates.ContentFieldTextFormat",

• "Capitalization":"None"

• }

• },

• {

• "FieldName":"RIC",

• "Justification":"Left",

• "Label":" ",

• "Width":-1,

• "WidthStyle":"VariableWidth",

• "Format":{

• "@odata .type":"#DataScope.Select.Api.Extractions.ReportTemplates.ContentFieldTextFormat",

• "Capitalization":"None"

• }

• },

• {

• "FieldName":"Universal Close Price",

• "Justification":"Left",

• "Label":" ",

• "Width":28,

• "WidthStyle":"VariableWidth",

• "Format":{

• "@odata .type":"#DataScope.Select.Api.Extractions.ReportTemplates.ContentFieldNumberFormat",

• "DecimalPlaces":9,

• "DecimalSeparator":"Period",

• "IntegerPlaces":18,

• "UseLeadingZero":false,

• "NegativeSignPosition":"Before",

• "ThousandSeparator":"Comma",

• "UseThousandSeparator":false,

• "UseTrailingZero":false

• }

• },

• {

• "FieldName":"Trade Date",

• "Justification":"Left",

• "Label":" ",

• "Width":-1,

• "WidthStyle":"VariableWidth",

• "Format":{

• "@odata .type":"#DataScope.Select.Api.Extractions.ReportTemplates.ContentFieldDateFormat",

• "DateFormat":"yyyy-MM-dd"

• }

• }

• ],

• "Condition":{

• "ReportDateRangeType":"Range",

• "QueryStartDate":"2023-04-04T00:00:00Z",

• "QueryEndDate":"2024-01-01T00:00:00Z",

• "AdjustedPrices":false,

• "LastEntityOnly":false

• }

• }

No error returned and the result code is 204, but the template is not updated.

Could you please advise if any change is required in this PUT?

Many thanks for your help.

Pietro

Below is my request body and I want to include CAP, DIV, and MNA together as CorporateActionsStandardEventsType within a single API call.

{
"ExtractionRequest": {
"@odata .type": "#DataScope.Select.Api.Extractions.ExtractionRequests.CorporateActionsStandardExtractionRequest",
"ContentFieldNames": [
"Security Long Description",
"ISIN",
"SEDOL",
"RIC",
"Dividend Ex Date",
"Capital Change Ex Date",
"Effective Date",
"Deal Effective Date",
"Dividend Pay Date",
"Dividend Payment Type Description",
"Capital Change Event Type Description",
"Dividend Currency",
"Dividend Currency Description",
"Dividend Rate",
"Dividend Tax Marker Description",
"New Shares Terms",
"Old Shares Terms",
"Offer Price",
"Offer Price Currency",
"Capital Change New Security ISIN",
"Corporate Action Notes"
],
"IdentifierList": {
"@odata .type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "7144569",
"IdentifierType": "Sedol"
}
],
"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
},
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"ReportDateRangeType": "Range",
"QueryStartDate": "2025-01-15",
"QueryEndDate": "2026-01-20",
"ExcludeDeletedEvents": true,
"IncludeDividendEvents": true,
"CorporateActionsDividendsType": "DividendExDate",
"IncludeInstrumentsWithNoEvents": false,
"IncludeNullDates": false,
"ExcludeDeletedEvents": true,
"IncludeCapitalChangeEvents": true,
"IncludeDividendEvents": true,
"IncludeEarningsEvents": false,
"IncludeMergersAndAcquisitionsEvents": true,
"IncludeNominalValueEvents": false,
"IncludePublicEquityOfferingsEvents": false,
"IncludeSharesOutstandingEvents": false,
"IncludeVotingRightsEvents": false,
"CorporateActionsCapitalChangeType": "CapitalChangeExDate",
"CorporateActionsDividendsType": "DividendExDate",
"CorporateActionsEarningsType": "EarningsAnnouncementDate",
"CorporateActionsEquityOfferingsType": "AllPendingDeals",
"CorporateActionsMergersAcquisitionsType": "DealEffectiveDate",
"CorporateActionsNominalValueType": "NominalValueDate",
"CorporateActionsSharesType": "SharesAmountDate",
"CorporateActionsStandardEventsType": "CAP",
"CorporateActionsVotingRightsType": "VotingRightsDate",
"ShareAmountChoice": "All",
"ShareAmountTypes": [
"Outstanding"
],
"ExcludeHistoricalEvents": false,
"LastEntityOnly": false
}
}
}

Can you suggest what to do here?

      "NextDays": 5,

We assume that this filter should filter the data based on Dividend Ex Date from T-3 to T+5, like what we get from below template where we have selected date range.If its different, then please suggest us how we can put date range in API body, our need is to achieve same date filter logic via API call as mentioned in below screenshot?

One major client is doing a GovCorp search via API and the response from the API is limited compared to the results in the GUI (I am able to reproduce it). They are specially interested in getting if the bond is a corporate or government bond.

Fields responded by the API with GovCorpSearch:

{'Identifier': 'XS3102778191', 'IdentifierType': 'Isin', 'Source': 'UTT', 'Key': 'VjF8MHgwMDEwNTUxYzBkODcxYmM4fDB4MDAxMDU1MDBiZTkxMWI3MXxVVFR8R0NCRHx8fEd8RXxYUzMxMDI3NzgxOTE9VVNUV3w', 'Description': "REP 4.500 Perp '31 FRN", 'InstrumentType': 'GovCorpBond', 'Status': 'Valid'}

Indeed the response from the GVOCorpSearch is the same answer as with a generic InstrumentSearch (weird).

{'Identifier': 'XS3102778191', 'IdentifierType': 'Isin', 'Source': 'UTT', 'Key': 'VjF8MHgwMDEwNTUxYzBkODcxYmM4fDB4MDAxMDU1MDBiZTkxMWI3MXxVVFR8R0NCRHxDT1JQfENGSU58R3xFfFhTMzEwMjc3ODE5MT1VU1RXfA', 'Description': "REP 4.500 Perp '31 FRN", 'InstrumentType': 'GovCorpBond', 'Status': 'Valid'}

GUI GovCorp Search shows "Debt Type" and other fields.

Can you please ley me know if we are doing something incorrectly ? Is it possible to perform a bond search and retrieve the Debt Type ?

Thanks

Could you please confirm the location of the SOAP WSDL file after this DNS change?

The previous location was

selectapi.datascope.refinitiv.com/datascopeapi/v1/extractionservice.asmx?wsdl

so I assumed that the new one would be

selectapi.datascope.lseg.com/datascopeapi/v1/extractionservice.asmx?wsdl

But this new WSDL file still refers to refinitiv.com in two places:

<!--  SERVICE  -->

<wsdl:service name="ExtractionService"><wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">Provides operations that support extractions.</wsdl:documentation>

  <wsdl:port name="ExtractionService" binding="tns:ExtractionService">

  <soap:address location="https://selectintapi.datascope.refinitiv.com/DataScopeApi/v1/ExtractionService.asmx"/>

  </wsdl:port>

  <wsdl:port name="ExtractionService1" binding="tns:ExtractionService1">

  <soap12:address location="https://selectintapi.datascope.refinitiv.com/DataScopeApi/v1/ExtractionService.asmx"/>

  </wsdl:port>

</wsdl:service>

Is this intentional?

2)

Also, the current version of the DSS .NET SDK is 19.1 https://developers.lseg.com/en/api-catalog/datascope-select/datascope-select-rest-api/download

This version was updated on 2025-12-26. Does it contain the new DNS changes?

Please advise how I should respond.