[Hasnain jaffery]

I tried this for APPLE and it does not work at all. SEC must provide something standard as per document “XBRL Application Programing Interface (API) version 1.4 Draft” Page 17 talks about table REPORTS where there is a field by the name entity.ticker. But in actual this field does not exist in the table “Field”.
Regards,
Hasnain

[Tim Bui]

Hi Hasnain, would you please elaborate what data that you wanted to get but couldn’t? Per your email, The CIK of “320193” is correct for APPLE
(https://www.sec.gov/cgi-bin/viewer?action=view&cik=320193&accession_number=0001193125-20-139112&xbrl_type=v)

I am able to get all of the CIK and their corespondent ticker from the SEC Financial Statement Data Set (FSDS).

I am not sure if XBRL US allows, but if it does, I can upload the list of CIK and Ticker that I derived form the FSDS for you to peruse.

Tim

[Hasnain jaffery]

Thanks Tim, I agree based on CIK list you can pull all the data from FSDS. but to me one the basic thing is missing which is the ticker and its history. For example some companies they merged together or bought out by another cone and ticker got changed. Without having ticker the SEC information seems to be little incomplete.
All I am trying to do it build a search to FSDS reports (including historic as well) based on ticker and at the moment it doesn’t seems to be that easy.
Can you share that with me at hjaffery@yahoo.com?
thanks

[Hasnain jaffery]

I am new to XBRL and I am a student at a very basic level, so I might be incorrect, if so please correct me I would highly appreciate it.
I need to cite the example of APPLE and compare it with MSFT (as you have used as an example)
If you check MSFT for this last quarter
CIK NAME FORM Period Instance
789019 MSFT 8-K 20200131 d875975d8k_htm.xml
789019 MSFT 10-Q 20191231 msft-10q_20191231_htm.xml
320193 AAPL 8-K 20200131 a8-kq1202012282019_htm.xml
320193 AAPL 10-Q 20200129 a10-qq1202012282019_htm.xml

May be I am wrong, please correct me. But based what I see the logic you have provided is not going to work.
Would be happy to discuss this with you in more detail
Regards,
Hasnain

[Hasnain jaffery]

I have found the other way to get this ticker. you can use the one of the provided functions (TICKER)

[Tim Bui]

Hello, Hasnain,
As you can see from the examples you provided, the “funny” codes on the xml lines related to the ‘8-K’ reports. The ticker codes are correct for ’10-K’ or ’10-Q’. I had to narrow to screen down to only ’10-K’ or ’10-Q’ to get the ‘Instance’ that contain the tickers.

I had emailed you the list of CIKs and Tickers that I derived from the FSDS.

I have not attempted to get historical Tickers or CIKs, but from seeing that the sub.txt file within FSDS has columns named “former” and “changed” for former name sand change dates, I think it is possible to get that information.

Regards,
Tim

[Hasnain jaffery]

Thanks Tim for the file. I agree the logic you provided works for 10-K and not for the others. 10

[Arthur Olevskiy]

Hi guys, I don’t know if it helps you but I’m using this json file
https://www.sec.gov/files/company_tickers.json

[Arthur Olevskiy]

Hi,

Can somebody answer me, please. Somewhere on this site I saw information that I can get data of non-US companies. Is it true and if yes, what data I can get and what countries this data covers?

Also, I wondered, can I retrieve textual data from 10-K and 10-Q and what SEC filings I can get from XBRL API except 10-K and 10-Q?

Thank you.

[Tim Bui]

Thanks so much for sending the link, Arthur! I didn’t even know this file exists. Thanks again!

[david.tauriello@xbrl.us]

Hi Arthur – thanks for writing. below is a list of forms submitted to the SEC that we collect and store in the XBRL Database of Public Filings – foreign private issuers submit their financial data to the SEC on 20-F and 40-F. We’re also exploring how to load reports from other US agencies and regulators in other jurisdictions.

XBRL US Members can use Company Filings Analysis in our SEC Filer Tools to search the text of documents in our Public Filings Database. We’re currently finalizing API endpoints for XBRL US Members that will provide this functionality via the XBRL API.

• 10-12G
• 10-12G/A
• 10-K
• 10-K/A
• 10-KT
• 10-KT/A
• 10-Q
• 10-Q/A
• 10-QT
• 20-F
• 20-F/A
• 20FR12G
• 40-F
• 40-F/A
• 424B3
• 485APOS
• 6-K
• 6-K/A
• 8-K
• 8-K12B
• 8-K12B/A
• 8-K/A
• ARS
• F-1
• F-1/A
• F-3ASR
• F-4
• F-4/A
• POS AM
• POS EX
• S-1
• S-11/A
• S-1/A
• S-3/A
• S-4
• S-4/A

[Arthur Olevskiy]

Thank you David.

[Arthur Olevskiy]

Hi,

Sorry if it was asked already.
I use this endpoint to get concept.local-name and fact.value data:

https://api.xbrl.us/api/v1/report/11572/fact/search?fields=period.calendar-period,concept.local-name,fact.value

Unfortunately, I didn’t figure out with following issues:
1. How I can get only facts from cash flow/income/balance sheet statement?
1.1 By the way, what parameters I can use for network.role-description= …
2. Can I get both facts base taxonomy and company specific taxonomy?

Thank you so much.

[Teji Abraham]

Hi David:
I have seen some issues with Operating Lease data and posting here to both raise awareness and also to inquire if there are any causes/solutions for these. Not sure if this is because of wrong xbrl filing from the company or some other reasons

So the typical type of problems found are:
a) Operating Lease total not adding up to the current and non-current components of Operating Lease
b) Scale of Operating Lease data being wrong
c) Mixing up of various operating lease data elements

Thanks and look forward to your inputs.

Example 1:
Fonar Corporation
Period: 2019-12-31, cik: 0000355019

Per SEC Filing (all in thousands):
Operating Lease Liability: 31,867
Operating Lease Liability Current: 3185
Operating Lease Liability Non-Current: 28682

Per XBRL data feed (all in thousands):
Operating Lease Liability: -987
Operating Lease Liability Current: 3185
Operating Lease Liability Non-Current: 28682

Note: the negative Operating Lease Liability total despite the positive sub-components

Example 2: (Scale of one of data components off by a factor of 1000)
SecureWorks Corp
Period: 2020-01-31, cik: 0000355019

Per SEC Filing (all in thousands):
Operating Lease Liability: 29,554
Operating Lease Liability Current: 4,885 (implied, ie calculated)
Operating Lease Liability Non-Current: 24,669

Per XBRL data feed (all in thousands):
Operating Lease Liability: 29,554,000
Operating Lease Liability Current: NIL
Operating Lease Liability Non-Current: 24,669

Example 3: (Mixed up operating lease data elements)
American River Bankshares
Period: 2019-12-31, cik: 0001108236

Per SEC Filing (all in thousands):
Operating Lease Liability: 3098
Operating Lease Liability Current: 769
Operating Lease Liability Non-Current: 2329 (implied)

Per XBRL data feed (all in thousands):
Operating Lease Liability: 915
Operating Lease Liability Current: 3098
Operating Lease Liability Non-Current: NIL

Note: Two issues in this example: total Operating Lease Liability is presented as Operating Lease Liability Current and values don’t add up accurately.

[david.tauriello@xbrl.us]

Hi Arthur – please see https://xbrl.us/forums/topic/extracting-data-from-a-particular-financial-statement for how to get statement data. There’s also a Google Sheet template – https://xbrl.us/xbrl-api-explorer with queries that might be helpful.

The network.role-description parameter is a text field. It can be manipulated with a stringmatch parameter using a couple of options (this needs to be added to our documentation):

• use like to find the string – https://api.xbrl.us/api/v1/relationship/search?dts.id=306447&network.link-name=presentationLink&network.role-description=consolidate income&stringmatch=network.role-description(like)&fields=network.role-description,relationship.id.sort(ASC),relationship.tree-sequence.sort(ASC),relationship.target-name

  returns nothing because the string consolidate income doesn’t exist in this network.role-description – remove one of the terms and you get results.

• use ts to find when each word in the string exists – https://api.xbrl.us/api/v1/relationship/search?dts.id=306447&network.link-name=presentationLink&network.role-description=consolidate income&stringmatch=network.role-description(ts)&fields=network.role-description,relationship.id.sort(ASC),relationship.tree-sequence.sort(ASC),relationship.target-name

Last, unless you’re using the ‘concept.is-base’ parameter to filter facts, the query will return both base and extension concepts (see documentation https://xbrl.us/xbrl-api-documentation).

[Author]

Posts