Filtering for English Annual Reports of German Companies via RDP Search & Filings API

Hi Developer Community,
I'm working on a project to download English-language annual reports for German listed companies (from 2018-2024) using the Refinitiv Data Platform APIs, specifically the Search API (/search/beta1/
) and the Filings GraphQL API (/data-store/v1/graphql
). I've made some progress but have hit a couple of key roadblocks where your expertise would be invaluable.
My Current Approach & Successes:
- Authentication: Successfully obtaining an access token using password grant with the
trapi
scope. - Identifying German Organizations (Search API -
/search/beta1/
):- Using
View: "Organisations"
. - Filtering with
RCSCountryHeadquartersLeaf eq 'Germany' and OrganisationStatus xeq 'Listed'
. - Using
Select: "_debugall"
to inspect the full response. - Successfully extracting the Organization PermID from
raw_source.OAPermID
(e.g., for Bertelsmann SE & Co KgaA, OAPermID:5037662836
).
- Using
Current Challenges & Questions:
1. Regarding the Search API (/search/beta1/
with View: "Organisations"
):
- Is
raw_source.OAPermID
the definitive and most reliable field for obtaining the Organization PermID when usingView: "Organisations"
? - Is there a more direct way to request the Organization PermID in the
Select
clause for this view, rather than relying on_debugall
(which returns a very large payload)? We've found that directly selectingPermID
at the top level of the hit does not yield the Organization PermID in this view.
2. Regarding the Filings GraphQL API (/data-store/v1/graphql
):
- Primary Issue: Null DocumentSummary
- Fields: When querying for filings using a valid OrganizationId (e.g., 5037662836 for Bertelsmann) and a date range, even if we remove all FormType or HighLevelCategory filters to get all document types, the fields within DocumentSummary (specifically DocumentTitle, FilingDate, FormType, DocumentType, FeedName, HighLevelCategory) are consistently returning null for all retrieved filings. Is this an expected behavior for certain filings/companies?
- Could this be an entitlement issue where the DocId is accessible but the detailed metadata within DocumentSummary is restricted for my App Key/user?
- Or is there a different way to select these fields if they are nested differently than expected?
- Identifying English Annual Reports (Server-Side):
- What are the specific FormType codes that should be used in the GraphQL filter to reliably identify English-language Annual Reports for German/European companies? (e.g., the equivalent of "10-K" for US filings). We have tried "AR" and "GBR" without success (returned 0 filings for Bertelsmann, suggesting these are not the right codes or are not used for this company).
- Is there a recommended DocumentType or HighLevelCategory value that specifically targets English annual reports for this region? The "Filings Service Developer Guide" (Nov 2020 version) has examples for US filings but lacks a comprehensive list for other regions/report types.
- Language Filtering:
- Is there a way to directly filter filings by language (e.g., for "English") within the GraphQL query?
Goal:My ultimate goal is to reliably identify and download the PDF documents for English-language annual reports for a list of German companies between 2018-2024. Or to download the letter to shareholders sections of those reports in eg. a csv file.
Any guidance, examples, or pointers to more detailed documentation on the DocumentSummary
fields for the Filings API, or correct FormType
codes for European annual reports, would be immensely appreciated!
Thank you for your help!
Answers
-
Thank you for reaching out to us.
We have the /discovery/search/v1 endpoint for search. You can refer to this Building Search into your Application Workflow article.
For Filings, you can refer to the Introduction To Filings - Python article for contact the Filings - Delivery Platform support team directly via MyAccount.
This forum is dedicated to software developers using LSEG APIs. The moderators on this forum do not have deep expertise in every bit of content available through LSEG products, which is required to answer content questions such as this one.
The best resource for content questions is the Helpdesk support team, which can be reached by submitting queries through MyAccount. The support team will either have the required content expertise ready available or can reach out to relevant content experts to get the answer for you.
1 -
Thanks for the quick reply! I will try the v1 route.
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
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛