Home › Forums › The XBRL API › Multiple Dimension Levels
- This topic has 1 reply, 2 voices, and was last updated 3 years, 8 months ago by David Tauriello.
-
AuthorPosts
-
-
Wednesday, March 23, 2022 at 7:43 AM #198917John SummersgillParticipant
Hi, I’m trying to qenerate a query to access 3 known concepts across 8 known entities. The issue I’m having is those concepts sometimes having multiple dimensions levels (not of proper nomenclature).
As an example I’m query entity CIK ‘0000896159’ for concept ‘PremiumsEarnedNet’. I have parameter to local only for member.local-name ‘SegmentGlobalReinsuranceMember’. The issue is that there is another dimension nested underneath that gets pulled into the query as well. What’s the best way to filter out the second dimension level? Below are the two dimensions returned. I only want the first one.
[{‘dimension_namespace’: ‘http://fasb.org/us-gaap/2021-01-31’, ‘dimension_local_name’: ‘StatementBusinessSegmentsAxis’, ‘member_namespace’: ‘http://investors.chubb.com/20211231’, ‘member_local_name’: ‘SegmentGlobalReinsuranceMember’}]
[{‘dimension_namespace’: ‘http://fasb.org/us-gaap/2021-01-31’, ‘dimension_local_name’: ‘StatementBusinessSegmentsAxis’, ‘member_namespace’: ‘http://investors.chubb.com/20211231’, ‘member_local_name’: ‘SegmentGlobalReinsuranceMember’},
-
{‘dimension_namespace’: ‘http://fasb.org/us-gaap/2021-01-31’, ‘dimension_local_name’: ‘SubsegmentsAxis’, ‘member_namespace’: ‘http://investors.chubb.com/20211231’, ‘member_local_name’: ‘PropertyandothershorttailMember’}]
-
Wednesday, March 23, 2022 at 8:05 AM #198967David TaurielloKeymaster
Hi John – thanks for the email follow-up (our system moderates any posts with URLs, and the queue is checked a couple times a week).
I think you’re on the right track filtering with
dimensions.countcombined with the specificmember.local-name(note that dimensions.count is plural – https://xbrlus.github.io/xbrl-api).This seems to be headed in the right direction:
/fact/search?entity.cik=0000896159&concept.local-name=PremiumsEarnedNet&period.fiscal-period=Y&fact.ultimus=true&fields=entity.name,period.fiscal-year.sort(DESC),fact.numerical-value,member.local-name,dimensions&member.local-name=SegmentGlobalReinsuranceMember&dimensions.count=1
Reply on the thread if you have additional questions about this or if it’s not quite right.
-
-
AuthorPosts
- You must be logged in to reply to this topic.
Search Forums
Recent Topics
- Income Statement data for a company by David Tauriello
- Normalized data presentation by David Tauriello
- Extract Director RSUs/Options Form 14A by Priyanka Goonetilleke
- Using the offset parameter by David Tauriello
- Spreadsheet Commands: Query Worksheet and Query Workbook Query Workbook by Liam Noailles
Recent Replies
-
Income Statement data for a company 5 months, 2 weeks ago
-
Income Statement data for a company 5 months, 2 weeks ago
-
Using the offset parameter 9 months, 3 weeks ago
-
Using the offset parameter 9 months, 3 weeks ago
-
Using the offset parameter 9 months, 3 weeks ago
Documentation & Discussion
- Get started with Google Sheets OR
- Get started with Microsoft Excel OR
- Get access to as-filed data from us for other tools or your own app
- XBRL API Interactive Documentation
- Ten Tips & Techniques
- The XBRL API
- XBRL Data Community
- 2024 US GAAP Taxonomy Viewer
- Live support - Monday, 3:30 - 4:30 PM ET
Who's using this free data?
API Use 2024 || API Use 2023 || API Use 2022 || API Use 2021 || API Use 2020 || API Use 2019 || API Use 2018
Join XBRL US
- Individual Options - Basic, Power User & Sole Practitioner
- For Your Team - Startup, Non-Profit, Academic & Corporate options
- Member Benefits Comparison Table
Using the XBRL API with the Public Filings Database
Unless otherwise agreed to in writing, any and all use of the XBRL API to authenticate and retrieve data from the XBRL US Database of Public Filings implies user consent and agreement with the XBRL US API Agreement. If you are unable to agree to these terms, do not use the XBRL API.
To use the XBRL API outside of Google Sheets, your account needs to be provisioned for OAuth2 access.





