DSS REST API - Entity/Instrument List automated update

Question about DSS REST API for a client, whose universe of Legal Entities is changing on a baily basis. Although it refers to EntityList specifically, but the same applies to InstrumentList.
Client is not happy with the fact that when using REST API, he has to build a new EntityList for every API call. Instead, he would like to insert an EntityList ID into API request/call – this list would be updated on a daily basis. So he would like to use a similar mechanism as with FTP, where the list of instruments/entities is updated on client’s server and linked to DSS schedule.
Is there a way that within the request (API call) the user can point to ‘EntityList’ Id, instead of having to build the standard request (API call) with all the entity Ids enumerated within?
Best Answer
-
Below an example, the training reference are the 2 links below:
ReplaceAllWithIdentifiersWithOptions https://hosted.datascopeapi.reuters.com/RestApi.Help/Context/Operation?ctx=Extractions&ent=EntityList&opn=ReplaceAllWithIdentifiersWithOptions
Example:
I created an entity list named Aleksandra_Entities:
First get the entity List ID by making a GET on:
answer is:
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#EntityLists/$entity",
"ListId": "0x0776a0a40a974ddd",
"Name": "Aleksandra_Entities",
"Count": 1,
"Created": "2021-03-03T05:02:08.903Z",
"Modified": "2021-03-03T05:02:47.973Z"
}
Then to update it [in a FTP like fashion which is a full replace] use the following [I am replacing adidas with puma and Nike in the list]
With the following payload:
{
"Identifiers": [
{
"Identifier": "NKE",
"IdentifierType": "Ric",
"UserDefinedIdentifier": "UserIdentReplace"
},
{
"Identifier": "PUMG.DE",
"IdentifierType": "Ric",
"UserDefinedIdentifier": "UserIdentReplace"
}
],
"Options": {
"AllowDuplicateInstruments": false,
"IncludeParentAndUltimateParent": false,
"AllowUnmanagedOrUnverifiedEntities": true
}
}
Then the list is updated:
0
Answers
-
Hello @aleksandra.kluczniak_refinitiv,
Can we please confirm, which part fails for the client?
They are using scheduled extraction request, not on demand ad-hoc, right?
They have created an EntityList?
They are submitting ListId of their EntityList into Schedule->Create?
They update EntityList?
Please provide any details that are relevant to better understand the issue,
Thanks
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
- 25 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
- 716 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 中文论坛