Forum Replies Created
-
AuthorPosts
-
Campbell PrydeParticipant
Unfortunately there is no unique identifier to identify a set of iles that comprise a taxonomy. We assign the dts id so at least we can reference a given taxonomy consistently. The US GAAP taxonomy for 2019 has a dts as does a companies extension taxonomy.
In addition the api provides a dts hash. This is a hash of the documents comprising a dts and two identical taxonomies should have the same hash. This also is not a standard yet.
Campbell PrydeParticipantJust to clarify the concept id and to clear up any confusion. The concept id represents a combination of the namespace and local name. So assets in the 2019 taxonomy will have a consistent concept id number. If you request fact values based on this number you will only get the values for Assets that used the 2019 taxonomy. To get the value of Assets irrespective of the taxonomy used the use the local-name called Assets. So a term like Assets will have at least 12 different concept ids associated with it for each different taxonomy included in the underlying dataset.
Searching on the local-name should be fast as this is indexed, but searching on concept.id will be faster as their are less records.
Theoretically companies should not define an extension called Assets as it is already defined in the US GAAP or IFRS taxonomy. However, if they do these can be excluded by seting the is-base parameter to true. This will exclude any extension elements.
Tuesday, June 25, 2019 at 9:44 AM in reply to: Extracting Data From A Particular Financial Statement #143867David TaurielloKeymasterHi Tim – I’m writing to let you know that the
relationship
endpoint has been updated to support simple text string search (as was done withlabel
earlier this year), so a query like this will return ‘cash flow’ statements for multipledts.id
s:/relationship/search?dts.id=292503,306447&network.role-description=cash flow&network.link-name=presentationLink&relationship.target-is-abstract=false&fields=dts.id.sort(ASC),relationship.id.sort(ASC),network.role-description,relationship.target-name,relationship.tree-sequence.sort(ASC),relationship.source-namespace
We’re in the process of updating documentation for this change.
Benjamin FenigsohnParticipantHow far back does MSFT, AAPL, and AMZN go? Is there an easy way to tell the year of historic data?
David TaurielloKeymasterHi Elmhurst – each fact tagged in an instance has metadata associated with it – including period details – making the XBRL data standard an excellent mechanism for analysis.
The query below summarizes reporting for the three companies in your post – drop this into the ‘config’ tab as a new row (give it a name), then select it from the Main Sheet dropdown to get results.
/fact/search?concept.local-name=EntityFilerCategory&entity.cik=0001018724,0000320193,0000789019&fields=entity.name,period.fiscal-year.sort(ASC),period.fiscal-period.sort(ASC),period.end,fact.value,report.sec-url,fact.offset(0)
Non-members will need to use the
fact.offset(xx)
switch to get later details. See #3 here: https://xbrl.us/forums/topic/how-to-get-a-sample-of-records-via-xbrl-api-for-evaluation/#post-116618 or ‘Paging’ in https://xbrl.us/xbrl-api-documentation for details.Anil ShrivastavaParticipantDear Friends,
I’m enjoying using the API and got my python scripts to pull a large number of historical financials for many tickers.
However, ticker MTSC, CIK 68709, only pulls financials from 2015 and before. It does not pull for 2016 – 2018. The SEC does have financials reported for MTSC for these periods. Could you take a look at the issue?
Thank you,
Anil.
David TaurielloKeymasterAnil – thanks for writing; this was similar to a prior post – https://xbrl.us/forums/topic/missing-reports/ and it has been resolved. Let us know if you find other instances.
Keep enjoying the data and please consider XBRL US Membership – https://xbrl.us/membership – for yourself or your institution to take full advantage of our Public Filings Database and other benefits.
Tim BuiParticipantI spent several days looking for the most up-to-date list of CIKs and their correspondent TICKERs and I found a solution that wanted to share with some of you, in case someone is trying to do the same thing.
1. The SEC has a link where it posts all of the quarterly filings (Financial Statement Data Sets)
https://www.sec.gov/dera/data/financial-statement-data-sets.html
2. You can download the zip file of the most recent quarterly filing (as of now 2019 Q2). After extracting, within each zip file are num.txt, pre.txt, sub.txt, tag.txt and a readme link.
3. The sub.txt holds all of the information of each of the submissions. Within it is a column named INSTANCE. The readme describes INSTANCE as “The name of the submitted XBRL Instance Document (EX-101.INS) type data file. The name often begins with the company ticker symbol.”
The INSTANCES for MSFT would look like the list below:
msft-20090930.xml
msft-20091231.xml
msft-20100331.xml
4. You can use your favorite program such as Excel or Python to strip out the characters to the left of the hyphen to get the tickers.I use this code in SQL to get the tickers:
upper(substring(sub.instance,0,CHARINDEX(‘-‘,sub.instance))) as TickerSince some of the filings do not have tickers at the beginning,
I use this SQL code to get tickers with 5 characters or lesswhere len(substring(sub.instance,0,CHARINDEX(‘-‘,sub.instance)) ) between 1 and 5
Regards,
Tim
Jason ZanfardinoParticipantThanks for the tip!
Tim BuiParticipantHi David,
Does XBRL US have a code to indicate if a CIK belong to a publicly-traded company, as opposed to a privately-held company?Thanks
David TaurielloKeymasterHi Tim – sorry for the delayed response. I’m not aware of any privately-held companies that have CIKs – can you give me an example – ?
FWIW – a query like this (changing offset) should give you a full list of alpha-sorted companies and tickers:
/report/search?report.is-most-current=true&fields=dts.id,report.entity-name.sort(DESC),entity.ticker,entity.id,report.offset(0)
Tim BuiParticipantHi David,
Thank you for your reply and for the code. I will use that code to see how far I get. The Financial Data Sets that I download contains so many CIKs and I try to narrow the list down to public companies or companies that have stock prices so I can make investment decisions.
Regarding the CIK for privately held companies, I assume that they are privately held because I can’t find any stock information on them. I always assumed that the SEC gives each filer a CIK, whether they are public or private. My confusion could also come from companies changing their names.
Examples of a few CIKs that I can’t find information:
1425392 – Grant Hartford Group.
1441082 – Lake Forest Minerals Inc
1111741 – Dynaresource Inc
1403570 – Quantum Materials CorpThanks again, David!
Tim
David TaurielloKeymasterFrom the CIKs you shared, it looks like Grant Hartford stopped filing in 2012; the others are still filing with the SEC (listed on OTCMKTS):
/report/search?entity.cik=0001425392,0001441082,0001111741,0001403570&report.is-most-current=true&fields=report.entity-name,entity.ticker,report.document-type,report.filing-date.sort(DESC),dts.id,entity.id,report.sec-url
There are some details on SEC’S CIK at the bottom of page 1: https://www.sec.gov/info/edgar/quick-reference/form-id.pdf
Teji AbrahamParticipantHi David,
I have run into some cases where I get differing values for the exact same concept, with same ultimus value. Any idea why this happens and how to address it to return a single valid value? See example below:
Thanks much.For e.g for AAL, cik=0000006201, fiscal year=2017, concept: OperatingLeasesFutureMinimumPaymentsDueCurrent returns the data below with two different values.
"data": [ { "concept.local-name": "OperatingLeasesFutureMinimumPaymentsDueCurrent", "report.type": "10-K", "period.fiscal-period": "Y", "period.fiscal-year": 2017, "fact.value": "2555000000", "fact.ultimus": true }, { "concept.local-name": "OperatingLeasesFutureMinimumPaymentsDueCurrent", "report.type": "10-K", "period.fiscal-period": "Y", "period.fiscal-year": 2017, "fact.value": "2572000000", "fact.ultimus": true } ]
Tuesday, September 17, 2019 at 11:38 PM in reply to: Why does XBRL return differing values for same concept and how to address it #151752David TaurielloKeymasterTeji – both values are valid; fact.id 195333267 is a dimensional fact of ConsolidatedEntitiesAxis / SubsidiariesMember (value = 2555000000).
Add fact.has-dimensions=false to your query to return non-dimensional facts.
-
AuthorPosts