Home › Forums › The XBRL API › Understanding ultimus, unique and accuracy-index in fact searches
- This topic has 0 replies, 1 voice, and was last updated 2 years, 5 months ago by David Tauriello.
-
AuthorPosts
-
-
Thursday, August 3, 2023 at 10:29 AM #212379David TaurielloKeymaster
A Member writes:
I’m trying to understand why a query using
fact.ultimus=truereports different results when I add theuniqueattribute (checkbox on XBRL Filed Data spreadsheet extension, or&uniquedirectly in the XBRL API query). Here’s the query without the &unique or &fact.ultimus=true attributes:https://api.xbrl.us/api/v1/fact/search?entity.code=0000940944&period.fiscal-year=2022&period.fiscal-period=Y&concept.local-name=NetIncomeLoss&fact.has-dimensions=false&fields=concept.local-name,fact.value,period.fiscal-period,period.fiscal-year,report.document-type,report.id- The
uniquefilter qualifies the request as “if this fact appears more than once in the results, just show it one time”.The phrase in the results is an essential characteristic of unique, which parses each row and drops all matches to leave a single case. If you add
fact.idto the fields displayed these values will be different for each and every fact, making the result set similar to the ALL results query. Note:uniquewill not drop instances where the spelling of a company name has changed across reports (eg. Nathan’s Famous Inc and Nathan’s Famous Inc. are two different spellings). - The
fact.accuracy-index=1filter operates on the report level to show the first instance of a fact meeting the query conditions. - The
fact.ultimus=truefilter says “show me the latest facts for this query” but does not respect the report (it evaluates all reports), so if the query excludes reports like DEF-14A because you’re looking only at 10-Ks, the results might not include the latest value.
The view below summarizes these distinctions. The left side of the worksheet applies
uniqueandultimuswithunique. In the latter case, the DEF-14A report matches the query.On the right side, additional display fields for ultimus and accuracy-index help illustrate why accuracy-index would be a better choice to get results if the query was restricted to 10-K reports.
- The
-
-
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 6 months, 3 weeks ago
-
Income Statement data for a company 6 months, 3 weeks ago
-
Using the offset parameter 11 months ago
-
Using the offset parameter 11 months ago
-
Using the offset parameter 11 months 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.






