Posting obo a client: Getting zero data from deal queries.

RogelynMayAgustin

Have been circling back to this and now getting a plethora of 403 errors for subscription entitlements on things that were drawing correctly before. Any idea who can assist here?My authentication is working correctly (getting HTTP 200 responses), but I'm receiving zero data from deal queries.

Examples:
Example 1 - Basic Deal Access:
Query: SCREEN(U(IN(DEALS)),TOP(5)) Fields: TR.NIIssuer
Expected Result: List of 5 company names from recent deals
Current Result: Only header row, no data rows

Example 2 - ECM-Specific Access:
Query: SCREEN(U(IN(DEALS)),TR.NIisECM=True,TOP(5)) Fields: TR.NIIssuer, TR.NIIssueDate, TR.NIProceedsAmtAllMkts
Expected Result: 5 ECM deals with company, date, and deal value
Current Result: Only header row, no data rows

Example 3 - Deal Manager Access:
Query: SCREEN(U(IN(DEALS)),TOP(5)) Fields: TR.NIIssuer, TR.NIManagers
Expected Result: Companies and their investment banking syndicates
Current Result: Only header row, no data rows

My authentication works (HTTP 200), but all three queries above return only header rows with zero data rows. I need these examples to work for ECM competitive analysis. Not certain why its giving a 403 error now, these draws were working a few days ago.

We've isolated the issue with our data access. Our LSEG Workspace authentication works and we can access company/equity data, but we have zero access to deal transaction data.

Technical Evidence:

• Working: Direct ticker queries (AAPL.O, MSFT.O) return company data and revenue
• Working: Company fields like TR.CompanyName, TR.Revenue
• NOT Working: Any DEALS universe queries return 0 rows
• NOT Working: All screeners using SCREEN(U(IN(DEALS))) format

Specific Test Results:

• AAPL.O,MSFT.O with TR.CompanyName: ✅ Works (2 rows)
• MSFT.O with TR.Revenue: ✅ Works ($281.7B)
• SCREEN(U(IN(DEALS)),TOP(1000)): ❌ 0 rows
• SCREEN(U(NewIssues),TOP(10)): ❌ 0 rows
• All deal-related universes: ❌ 0 rows

API Endpoint: POST http://localhost:9000/api/v1/data

Let us know how to best proceed

RogelynMayAgustin

REMOVED

Please do not post any user information on these public forums!!!

Gurpreet

Please do not post any user information on these public forums!!!

Is the user able to get deals data using the LD library?

They are trying to directly interact with API proxy. This mechanism is not supported and will also be deprecated in future releases of the Workspace/LD library.

Gurpreet

If the user needs REST API access, then please recommend enterprise products like LSEG Data Platform, Datascope, Tickhistory etc

RogelynMayAgustin

Hi @Gurpreet , I have checked and the same to the client and here is her reply:

 I was explicitly told that I could use the API locally to draw this information, also this endpoint was working fine until around a week ago. This is not an Api proxy this is a supported product by your team is it not? Can you please connect with our account managers to fix this.

Please advise.

https://community.developers.refinitiv.com/discussion/comment/127720#Comment_127720

https://community.developers.refinitiv.com/discussion/comment/127721#Comment_127721

Jirapongse

@RogelynMayAgustin

Please note that we are not the product support team.

Our role typically involves answering general or technical questions related to API usage and providing sample code snippets to help retrieve the required data.

For product-specific issues or support, please raise your query via LSEG Support.

If you can share the code used by the client, I’ll be happy to test it on my machine and assist further.

Moreover, 403 error could relate to the client network issue, such as proxy or firewall settings. The clients may contact their IT team to verify the network settings.

RogelynMayAgustin

https://community.developers.refinitiv.com/discussion/comment/127727#Comment_127727

Hi @Jirapongse I have pasted the code here but it was removed as it contains client information.
Is there a way to sent it to you privately so you can test it out?

Jirapongse

@RogelynMayAgustin

There are two issues.

1. We don't support this kind of usage. The client needs to use our LSEG Data Libraries (Python, .NET, and Typescript) to access the services from http://localhost:9000.
2. The following screener formulas also don't work on the Workspace Excel

SCREEN(U(NewIssues),TOP(10))
SCREEN(U(Deal),TOP(10))

Please contact the helpdesk team to verify these formulas.