Friday, December 14, 2018 at 1:06 PM #118639
Friday, December 14, 2018 at 1:06 PM #118640
Do you provide any historical trace for deprecated concepts? Could we trace the lineage of a concept between taxonomies using the API?
You could use the dts for approved base taxonomies (US GAAP, IFRS) to query concepts and look for ‘Deprecated’ in the label … something like:
If you do this for the example, you’ll see the element was deprcated as of 2016 US GAAP. This is not particularly effective, though, and in addition, FASB has moved the notation for deprecated concepts from the label to a reference, so the detail exists in two places.
We’ve got plans to implement string search in a couple of areas and these will be included (thanks for a great suggestion), so a query on ‘deprecat’ will pull only those values.
Thursday, December 20, 2018 at 11:54 AM #118962
Is there a way to go back from the data received through the API to the actual human-readable SEC filings where the data come from, to quickly double check the data for example?
On the webinar, we mentioned that you can use
report.sec-urlfrom the report endpoint to return the URL to the SEC index page for the filing. You can also use
report.entry-urlfor the location of the instance (facts) for the filing.
Further – if you combine the
fact.xml-idyou have a citation to the location of the fact within the instance (NOTE: not all facts have a corresponding xml id in EDGAR).
If you open the report.entry-url in a browser and use ‘find in page’ to search on the fact.xml-id value, it will bring you to the AOCI value.
- You must be logged in to reply to this topic.
XBRL API Resources
- The XBRL API
- XBRL Data Community
- XBRL API Interactive Documentation
- XBRL API Documentation (PDF)
- Get Started with Google Sheets
- OR request account provisioning to use Client ID and secret pairs in your app and:
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.
Ready to work with the API in Excel's Power Query, or with your own system or app?
Contact us at email@example.com to have your existing XBRL US Web account provisioned to generate client ID/Secret pairs to work with the XBRL API in a REST client or other application, including Excel's Power Query.
NOTE: You do not need to generate client ID/Secret pairs if you use the Google Add-on and Google Sheet exclusively to access data - the XBRL API Authentication Add-on handles this automatically.
Your account needs to be provisioned before you can login and generate client ID/secret pairs.
Login or register for a free account.
Join XBRL US
- Individual Options - Basic, Power User & Sole Practitioner
- For Your Team - Startup, Non-Profit, Academic & Corporate options
- Member Benefits Comparison Table