How to put identifiers into a request message in order not to how the 50 characters limit?

Below works where Identifier has 50 characters exactly. If I put 4 ISINs where the last one GB000718875 is incorrect, since I removed the last character “7”. Otherwise I exceed the 50 character limit:
{
"SearchRequest": {
"InstrumentTypeGroups": [
"CollatetizedMortgageObligations", "Commodities", "Equities", "Funds",
"FuturesAndOptions", "GovCorp", "Money", "MortgageBackedSecurities",
"Municipals"
],
"Identifier": "FI4000297767,SE0000242455,DK0010274414,GB000718875",
"IdentifierType": "Isin",
"PreferredIdentifierType": "Ric"
}
}
If I add the missing character “7” then I have 51 characters in total but then I get error:
"error":{
"message":"Validation Error:\r\n\r\nIdentifier can not exceed 50 characters"
}
So how to pass a list of identifiers including more than 50 characters e.g. “5” ISINs? Please advise.
Best Answer
-
it is not possible to pass a list that contains more than 50 characters, that limit must be respected.
If the instrument list is longer, then it needs to be split, and multiple requests submitted.
0
Answers
-
Thank you Christiaan.
So it is not possible to request data for more than 4 ISINs in a single API call? If I have e.g. 500 ISINs, what is the best way to obtain data for them with the use of API? Splitting them into 125 separate requests does not sound too good
0 -
The search request was initially meant for only 1 instrument. Consider it a bonus that you can query several (within the 50 character limit), using comma separated instrument identifiers :-)
Other DSS API calls work in a different way, and allow you to query many more instruments (within limits of course, but those limits are much higher, see the extraction limits help page). The DSS best practices and limits document might also be of help in this context.
To come back to your follow-up request, if you have 500 ISINs and need to run this search request on all of them, then yes, you will have to split your list and run 125 requests.
0 -
Thank you very much Christiaan for your thorough reply.
All the best,
Lukasz
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 24 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 713 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛