API related

SHIVU_SB_123456789

I am currently working through an Excel file containing approximately 500,000 rows and need to identify the corresponding LSEG ticker (or PermID for private companies without a listed ticker) for a subset of account holder names.

The account holder names are in Column A, and I would like to populate the associated ticker/PermID in Column B.

Is there an LSEG tool, API, Excel function, or recommended workflow that can return the best matching entity based on a company name? Ideally, the solution would handle cases where:

Company names differ slightly from their official listing names.
Legal entity suffixes (Ltd, PLC, Inc., etc.) vary.
Multiple potential matches exist and a confidence score or ranking can be provided.

My main concern is balancing match coverage with accuracy, as standard exact matching may both miss valid entities and incorrectly assign others.

Have you seen a recommended approach for large-scale entity matching exercises of this type?

I’ve been experimenting with the PermID API and noticed something I wanted to sense-check with you.

 

For the entity “Vasiliko Cement Works Public Company Ltd - Moni Cement Plant”, the API appears to return PermID 4298106960 (PermID record), which is associated with “Basiliko Cement Works.”

 

However, based on the listed entity and RIC, I would have expected the match to resolve to VASSILICO CEMENT WORKS PCL (VCW.CY) instead.

 

Could you please advise whether there is a more accurate way to query the API, or whether there are additional parameters or matching methods that would help ensure the result resolves to the correct legal entity (for example, prioritising listed issuers, RICs, or organisation records)?

 

n Figure 1, the fuzzy search returns a PermaID associated with Basiliko Cement Works. However, when using the standard Workspace search function and entering the same company name, the search returns VCW.CY (Vassiliko Cement Works PCL), which appears to be the correct entity, as shown in Figure 2.

 

Could you please clarify why the fuzzy search is mapping this company name to a different PermaID and whether this behaviour is expected?

 

Figure 1

Figure 2

Jirapongse

@SHIVU_SB_123456789

Thank you for reaching out to us.

We provide the PermID - Record Matching RESTful API, which enables users to match Person, Organization, Instrument, and Quote records to their corresponding PermIDs.

I tested it with the following entries.

organization="""
LocalID,Standard Identifier,Name,Country,Street,City,PostalCode,State,Website
1,,Vasiliko Cement Works,,,,,,
2,,Vasiliko Cement Works Public Company Ltd - Moni Cement Plant,,,,,,
3,,Tata Play Ltd,,,,,,
4,,Microsoft Corp,,,,,,
5,RIC:IBM.N|Ticker:IBM,,,,,,,
6,Ticker:MSFT,,,,,,,
7,LEI:INR2EJN1ERAN0W5ZP974,,,,,,,
8,Ticker:FB&&Exchange:NSM,,,,,,,
9,Ticker:AAPL&&MIC:XNGS,,,,,,,
"""

It returns 4295941210 for "Vassilico Cement Works PCL" and it couldn't match "Vasiliko Cement Works Public Company Ltd - Moni Cement Plant".

4295941210 returns VCW.CY in Workspace.

On the other hand, LSEG Data Libraries don't have this matching feature. It provides the Search API to search for entries.

df = ld.discovery.search(
    view = ld.discovery.Views.ORGANISATIONS,
    query = "Vassilico Cement Works PCL",
    select = "OAPermID,PrimaryRIC,CommonName")
df

However, it doesn't support bulk request like matching API. For more information, please refer to this Building Search into your Application Workflow article.

Regarding the client's questions:

Have you seen a recommended approach for large-scale entity matching exercises of this type?

I think the Matching API is well suited to this use case. However, you may want to contact your LSEG account team or sales representative to discuss and verify whether there are any alternative solutions that better fit your requirements.

Could you please advise whether there is a more accurate way to query the API, or whether there are additional parameters or matching methods that would help ensure the result resolves to the correct legal entity (for example, prioritising listed issuers, RICs, or organisation records)?

Please check the matching templates and instructions at https://permid.org/record-matching. . We encourage you to supply as much information as possible on a record in order to obtain the most accurate and reliable results.

Could you please clarify why the fuzzy search is mapping this company name to a different PermaID and whether this behaviour is expected?

To verify the behaviour of the Matching API, the client will need to share the file they are using for the matching process.