PermID ordering from /discovery/symbology/v1/lookup API
How do I correctly use the symbology lookup API to retrieve PermIDs for a list of SEDOLS (with potentially inactive SEDOLs on the list). I have used the showHistory=True functionality as suggested in an earlier Q&A
However, there appears to be a problem with the JSON output returned in that the PermID results returned are not necessarily in the same order as the SEDOL list.
In the example below, the first SEDOL 6499323 should be Kumho Petrol but Korea Electric is returned first.
Example body:
{
"from": [
{
"identifierTypes": [
"SEDOL"
],
"values": [
"6499323",
"6497112",
"6495730",
"6495428"
]
}
],
"to": [
{
"objectTypes": [
"organization"
],
"identifierTypes": [
"PermID"
]
}
],
"reference": [
"name",
"status",
"classification"
],
"type": "auto",
"showHistory": true
}
Thanks.
Best Answer
-
Hello @danny.lo the symbology API does not guarantee that output ordering is the same as the order of input values. The user guide p21 mentions 'There is no predefined sort order to the entities returned in the API response and sort order should not be programmatically relied on to be in a certain order'. I will investigate if this feature could be added in future.
0
Answers
-
hi @danny.lo ,
I tried to remove the parameter "showHistory" from the API request and found that the response contains the mapping between input/output identifiers. Please see more detail below.
- response of the request with showHistory parameter
{
"data": [
{
"input": [
{
"value": "6499323",
"identifierType": "SEDOL"
},
{
"value": "6497112",
"identifierType": "SEDOL"
},
{
"value": "6495730",
"identifierType": "SEDOL"
},
{
"value": "6495428",
"identifierType": "SEDOL"
}
],
"output": [
{
"value": "4295881588",
"identifierType": "PermID",
"objectType": "organization",
"name": "Korea Electric Power Corp",
"status": "Active",
"classification": "Utilities"
},
{
"value": "4295882003",
"identifierType": "PermID",
"objectType": "organization",
"name": "Korea Zinc Inc",
"status": "Active",
"classification": "Basic Materials"
},
{
"value": "4295881087",
"identifierType": "PermID",
"objectType": "organization",
"name": "Kumho Petro Chemical Co Ltd",
"status": "Active",
"classification": "Consumer Cyclicals"
},
{
"value": "4295881083",
"identifierType": "PermID",
"objectType": "organization",
"name": "CJ Logistics Corp",
"status": "Active",
"classification": "Industrials"
}
],
"effectiveFrom": "1997-10-22T00:00:00.000Z"
}
],
"requestId": "xxxxx",
"effectiveAt": "2022-06-21T06:48:00.623Z",
"messages": []
} - response without showHistory parameter
[
{
"input": [
{
"value": "6495730",
"identifierType": "SEDOL"
}
],
"output": [
{
"value": "4295881588",
"identifierType": "PermID",
"objectType": "organization",
"name": "Korea Electric Power Corp",
"status": "Active",
"classification": "Utilities"
}
]
},
{
"input": [
{
"value": "6495428",
"identifierType": "SEDOL"
}
],
"output": [
{
"value": "4295882003",
"identifierType": "PermID",
"objectType": "organization",
"name": "Korea Zinc Inc",
"status": "Active",
"classification": "Basic Materials"
}
]
},
{
"input": [
{
"value": "6499323",
"identifierType": "SEDOL"
}
],
"output": [
{
"value": "4295881087",
"identifierType": "PermID",
"objectType": "organization",
"name": "Kumho Petro Chemical Co Ltd",
"status": "Active",
"classification": "Consumer Cyclicals"
}
]
},
{
"input": [
{
"value": "6497112",
"identifierType": "SEDOL"
}
],
"output": [
{
"value": "4295881083",
"identifierType": "PermID",
"objectType": "organization",
"name": "CJ Logistics Corp",
"status": "Active",
"classification": "Industrials"
}
]
}
],
"requestId": "xxxxx",
"effectiveAt": "2022-06-21T07:16:04.568Z",
"messages": []
}
Hence, to get more information regarding the parameter "showHistory", case number 11341509 is raised on behalf of you and you'll be contacted by the specialist directly.
Hope this helps.
0 - response of the request with showHistory parameter
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛