- This topic has 2 replies, 2 voices, and was last updated 5 years ago by .
Viewing 1 reply thread
Viewing 1 reply thread
- You must be logged in to reply to this topic.
Home › Forums › The XBRL API › What's happening to the Data Analysis Toolkit?
In late 2015, we published our first set of APIs, documentation and related resources (Google Sheets, Microsoft Excel files) as a preliminary attempt at exposing data in the XBRL US Database of Public Filings – the Data Analysis Toolkit.
Among the feedback we received about the APIs was a consistent request to make them ‘easier for non-XBRL people’ to understand and implement. The XBRL APIs do that, and more, so we’ve decided to shut down the ‘legacy’ APIs associated with the Data Analysis Toolkit in December, 2018.
With participation from the XBRL Data Community in the form of live web exchange, submitted templates and support through these discussion forums, we expect interest in standardized financial data and a standard to retrieve the data will continue to grow.
Where can we get new keys if we want to continue using the data via a key and direct queries to the database?
Thanks for your interest in using data from the XBRL US Database of Public Filings. Anyone can use the XBRL API to return up to 1,000 records per query from the repository. To use the XBRL API in your own application for private, non-commercial research and development, send a request to have your XBRL US Web Account provisioned to info@xbrl.us.
Power User and Sole Practitioner Individual Members, as well as all Organizational Members, have access to all available data via the API, as well as direct queries to the Database. See the Member Benefits link under “Join XBRL US” at right to learn more and find out about the option that’s right for you and/or your team.
API Use 2023 || API Use 2022 || API Use 2021 || API Use 2020 || API Use 2019 || API Use 2018
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.