On Monday, November 16, 2026, the SEC EDGAR system took in 11,068 filings. Only 370 of them were Form 8-K, which is 3.3% of the day (daily index for that date). We also fixed a watchlist of 30 large US companies. The SEC submissions API showed 10,591 filings for them in 90 days. Two banks filed most of them: 81% were 424B2 pricing supplements.
The watchlist filed 87 Form 8-K reports in that window. EDGAR accepted 82 of them outside the regular 9:30 to 16:00 trading session in New York. Then we used the EveryInfra google_news/search capability to compare news times with three recent 8-K filings. For the NVIDIA CEO change, Google News already listed a related story before the 8-K. Its time was 14.7 hours earlier, but the story was updated later, so we do not count that as a lead. For the Home Depot and Disney earnings, the wire press releases also appeared in the news before the 8-K.
Key points
- One EDGAR day had 5,333 to 11,068 filings in our sample, and Form 8-K was only 3.3% to 4.4% of each day.
- In 90 days, 30 large companies filed 10,591 documents; 8,594 were 424B2, and only 5 of 87 8-Ks came in market hours.
- The XOM ticker moved from CIK 34088 to CIK 2115436 on July 1, 2026, and the old CIK still files.
- Of 437 companies that report revenue under two XBRL concepts, 257 show two different values for CY2026Q2.
- Four live data API calls cost $0.003168; one Google News and one Reddit check per 8-K cost about $0.14 per quarter.
From the full EDGAR feed to a few event cards for the owner, the system must filter out most documents. Illustration for this article
Select the monitoring task first: one day has more than 10,000 filings
First, look at the size of the full feed. The SEC publishes a daily index for each business day, sorted by form type (Developer Resources lists the daily-index folder). We downloaded the files for November 13, 16 and 17, 2026, at 16:14 UTC on November 18 (00:14 Singapore time on November 19). Then we counted the form types line by line.
The three days had 7,471, 11,068 and 5,333 filings. The largest day was more than twice the smallest day. Each day had 111 to 129 different form types.
| Date (ET) | Total filings | 8-K | 8-K/A | Form 4 | Amendments (/A) | 8-K share |
|---|---|---|---|---|---|---|
| 2026-11-13 (Fri) | 7,471 | 302 | 15 | 1,382 | 289 | 4.0% |
| 2026-11-16 (Mon) | 11,068 | 370 | 12 | 1,272 | 236 | 3.3% |
| 2026-11-17 (Tue) | 5,333 | 237 | 6 | 2,088 | 179 | 4.4% |
On November 16, the largest groups were SCHEDULE 13G (3,148) and 13F-HR (1,662). Both are holdings reports from institutional investors. Form 13F is due within 45 days after the quarter end (SEC Form 13F FAQ). The 2023 beneficial ownership rule also set quarterly 13G amendments at 45 days after the quarter end (final rule).
The 45th day after September 30 was Saturday, November 14. Under Exchange Act Rule 0-3, a deadline on a weekend moves to the next business day. Thus these reports came in on Monday, November 16, and that day became the largest of the three. If the volume doubles on one day, check the filing calendar first. Then check your own collector.
Suppose you send all of these filings to users as new events. Then an analyst who follows 30 companies must find a few relevant items in thousands each day. The table also shows the volume of amendments.
Each day had 179 to 289 filings with /A. These filings change content that a company already filed. A monitoring system must attach each one to its original filing. It must not show it as a new event.
Thus the first product version asks the user for three things. Which companies (legal entities) do you follow? Which events matter (forms and 8-K item numbers)?
Where must the result go? An example rule: "When one of these 30 companies files an 8-K with Item 5.02 or Item 2.02, make a review card with a link to the source." This scope is much smaller than "monitor all SEC filings". It is also easier to test. Our article on competitive intelligence data products discusses the same choice: first define a question that people act on, then select the data.
A form type helps you route a filing. It does not tell you how important the filing is. A Form 4 can be a routine option exercise or a large sale by a founder. An 8-K can be a routine vote result or a CEO resignation. Later sections show two real 8-K filings with the same item number and very different weight.
30 companies in 90 days: 81% of filings were 424B2
The full feed is not enough. You must also see the rhythm of one real watchlist. Before we collected data, we fixed a list of 30 tickers. The first 15 are Apple, Microsoft, NVIDIA, Amazon, Alphabet, Meta, Tesla, Berkshire Hathaway, JPMorgan Chase, Visa, Walmart, ExxonMobil, UnitedHealth, Johnson & Johnson and Procter & Gamble. The other 15 are Mastercard, Home Depot, Costco, Netflix, Oracle, Bank of America, Coca-Cola, PepsiCo, Chevron, AbbVie, Adobe, Salesforce, AMD, Intel and Disney.
We mapped each ticker to a CIK with the SEC file company_tickers.json. Then we read each submissions JSON file on data.sec.gov. The window was August 20 to November 18, 2026, which is 90 days.
The result was 10,591 filings. The largest form was 424B2, with 8,594 filings, or 81%. JPMorgan Chase filed 6,409 documents, and 5,608 of them were 424B2. Bank of America filed 3,197, and 2,976 of them were 424B2.
Banks file these pricing supplements when they issue structured notes. They are useful for issuance and trading teams. For most users who follow company news, they are noise. Without the two banks, the other 28 companies filed 985 documents in 90 days. That is about 2.7 filings per company per week, and 562 of them (more than half) were Form 4.
The banks set the pace for the full list. The list had filings on 62 days in the window, about 118 filings per calendar day on average. The busiest day was November 3, 2026, with 450 filings: 316 from JPMorgan Chase and 100 from Bank of America.
| Ticker | Filings in 90 days | 424B2 | Form 4 | 8-K | Amendments (/A) |
|---|---|---|---|---|---|
| JPM | 6,409 | 5,608 | 7 | 4 | 25 |
| BAC | 3,197 | 2,976 | 29 | 3 | 28 |
| PG | 119 | 0 | 73 | 7 | 1 |
| META | 79 | 0 | 34 | 4 | 0 |
| MSFT | 65 | 2 | 45 | 5 | 0 |
| WMT | 55 | 0 | 33 | 3 | 0 |
You must filter by form after you filter by company. If you do not, the two banks take 91% of the watchlist traffic. Also, every company filed at least one 8-K.
The total was 87 Form 8-K reports plus 2 Form 8-K/A amendments, which is 89. That is about one per company per month. For users who follow management changes, deals and earnings, these 89 filings are the main input. The 598 Form 4 filings are a second layer. They fit better in a separate insider trading view.
Procter & Gamble had 73 Form 4 filings, the most on the list. A Form 4 is due within two business days after the trade (SEC guide to Forms 3, 4 and 5). One vesting event can create several filings. A weekly summary per person ("net shares bought or sold this week") is closer to what users need than one alert per filing.
When you merge Form 4 data, use the transaction code. Each trade in Table I has a letter code. Open market purchases and sales, option exercises, grants and tax withholding all have different codes. Only open market trades show a decision that an insider made with personal money. Count how many of the 73 P&G filings remain after this filter during your pilot. Do not assume the number before you test.
The CIK is the stable key; the ticker is an alias
The SEC EDGAR API documentation says that you access submissions data by a ten-digit CIK with leading zeros. The response gives the current name, former names, exchanges and tickers. Our copy of company_tickers.json had 10,400 rows for 7,996 CIKs. Of these, 1,432 CIKs had more than one ticker, with 3,836 tickers in total.
The largest case was CIK 927971 (Bank of Montreal), with 45 tickers. Most of them are exchange-traded notes. Bank of America had 17 tickers, mostly preferred shares. Thus the step "the user types a ticker and the system finds one company" must handle one-to-many links.
A harder case is a ticker that moves from one CIK to another. We found one on our list. XOM now maps to CIK 2115436, named ExxonMobil Holdings Corp.
The first filing for this CIK is an 8-K12B on July 1, 2026. In a press release on June 22, 2026, ExxonMobil said that it would move from New Jersey to Texas. ExxonMobil Holdings Corporation would become the public parent company, and the shares would continue to trade as XOM. The 8-K12B of July 1 says that it establishes the new company as the successor registrant.
The filing detail page for the ExxonMobil Holdings 8-K12B. The teal boxes mark the acceptance time and the seven item numbers. Captured Nov 19, 2026, Singapore time. SEC EDGAR filing detail page
The old CIK 34088 (EXXON MOBIL CORP) did not disappear. Its submissions show a Form 25-NSE from the exchange on July 2. This form is a notice that the securities left the exchange (PDF on the ExxonMobil investor site). After that, the old CIK filed a 10-Q on August 3, a 424B2 and an FWP in September, and a SCHEDULE 13G/A on October 27.
Suppose a monitoring system set a subscription on CIK 34088 before July. After July, it continues to get debt filings for the old entity, but it does not get the 8-K filings of the new parent. Suppose the system set the subscription on the ticker. Then it mixes the filings of two legal entities into one timeline.
| Date | CIK 34088 (Exxon Mobil Corp) | CIK 2115436 (ExxonMobil Holdings Corp) |
|---|---|---|
| 2026-06-22 | Press release gives the July 1 effective date | No filings yet |
| 2026-07-01 | — | 8-K12B accepted 12:36:49 ET; several S-8 POS and POSASR filings on the same day |
| 2026-07-02 | Form 25-NSE | Starts to trade as XOM |
| 2026-08-03 | 10-Q | — |
| 2026-11-09 | — | 8-K (Items 8.01 and 9.01) |
| Read on 2026-11-19 | Empty tickers field | Tickers field is XOM, 43 filings |
Use the CIK as the entity key. Attach tickers, names and user aliases to the entity. When a ticker moves, mark the old CIK with "successor entity: 2115436". Do not move old events to the new entity, and do not delete old subscriptions. On the watchlist page, show the CIK, the current name and the latest filing together.
Then the user can see which legal entity stands behind XOM. A group can have several filers. Record which filer the user selected. If the user cannot decide, keep the item in a "to confirm" state. Do not merge entities only because their names look similar.
Each filing event must link back to the source documents
Do not remove duplicate events by title or by crawl time. Use the identifiers that the SEC gives. The SEC Webmaster FAQ explains the accession number. The first ten digits are the CIK of the entity that submitted the filing. This can be the company or a filing agent. The next two digits are the year, and the last digits are a sequence number for that submitter.
We checked the 89 Form 8-K and 8-K/A filings on our list. For 38 of them, the accession prefix was the CIK of a filing agent. If you use the accession prefix to find the company, you get the wrong answer in more than four of ten cases. Use the company CIK from the submissions file.
Store at least these fields for each event: company CIK, accession number, form type, filingDate, reportDate and acceptanceDateTime. Also store the item numbers, primary document, list of exhibits and the link to the index page. The display layer can show a short summary, but the base record must keep all fields.
The NVIDIA 8-K for Item 2.02 on November 17 has a typical structure. In addition to the main document, it has three exhibits: the earnings press release, the CFO commentary and supplemental financial data. It also has a set of XBRL files that contain only cover page data. If you read only the main HTML, you miss the press release. If you join all exhibits, you get duplicate text.
Select exhibits by question. For earnings, read the EX-99.1 press release. For detailed financial data, wait for the XBRL in the 10-Q. For management changes, read the Item 5.02 text in the main document.
For deals, read the agreement exhibits (EX-2.1 or EX-10). On each card, show which exhibit the result came from. The ExxonMobil 8-K12B has 6 documents and 7 item numbers. If you read only the first paragraph of the main document, you can think that it is a routine agreement.
Be careful with time fields. In submissions JSON, acceptanceDateTime is in UTC. For example, the ExxonMobil 8-K12B shows 2026-07-01T16:36:49.000Z.
The filing detail page for the same filing shows 2026-07-01 12:36:49, which is Eastern time. The SEC FAQ also says that the acceptance time in the header of the complete submission text file is Eastern time. If your system uses both sources, convert all times to one time zone when you store them. If you do not, the same filing can show a difference of four or five hours.
The filingDate field has one more rule. Regulation S-T Rule 232.13 says that most filings submitted after 5:30 p.m. Eastern time get the next business day as the filing date. There are two exceptions that keep the same day until 10 p.m. The first is Forms 3, 4 and 5, Schedule 14N, Form 144, and Schedules 13D and 13G, with their amendments. The second is a registration statement under Rule 462(b). SCHEDULE 13G was the largest form on November 16, so a 5:30 p.m. cutoff for all forms gives wrong dates for it. Two 8-K filings on our list crossed the 5:30 p.m. line.
PepsiCo filed an 8-K at 17:57:44 ET on October 7, and its filing date is October 8. Salesforce filed at 21:02:48 ET on September 16, and its filing date is September 17. If you sort events by filingDate, these two filings move to the next day. If you sort by acceptance time, you get the correct order.
We tested this rule on all 90 days of watchlist filings. EDGAR accepted 1,130 of them after 5:30 p.m. ET. The 293 filings in the 10 p.m. group (Forms 3, 4 and 144 and Schedules 13D and 13G) all came before 10 p.m., and all kept the same filing date. Of the other 837 filings, 830 got the next business day. Most were 424B2 (607), FWP (128) and 424B3 (75). Seven others kept the same date, and we did not check why. Thus a Form 4 accepted before 10 p.m. stays on the same day, but an 8-K or a 10-Q accepted after 5:30 p.m. moves to the next day.
Keep these time rules in one configuration table with their sources. When the SEC changes a rule, you change one row:
| Time rule | Current value | Source |
|---|---|---|
| Deadline for most 8-K items | 4 business days after the event | Form 8-K |
| Deadline for Form 4 | 2 business days after the trade | Forms 3, 4 and 5 |
| 13F and quarterly 13G amendments | 45 days after the quarter end | Form 13F FAQ |
| Filing date cutoff | 5:30 p.m. ET; 10 p.m. for Forms 3, 4, 5, 14N, 144, 13D, 13G and Rule 462(b) | 17 CFR 232.13 |
| Deadline on a weekend or holiday | Moves to the next business day | Rule 0-3 |
| Read rate limit | 10 requests per second per user | Developer Resources |
# Build events from submissions JSON. Key: (company CIK, accession). Store times with a time zone.
import json, datetime as dt
from zoneinfo import ZoneInfo
d = json.load(open("CIK0001045810.json")) # data.sec.gov/submissions/CIK##########.json
r = d["filings"]["recent"]
events = []
for i, form in enumerate(r["form"]):
if form not in ("8-K", "8-K/A"):
continue
acc_utc = dt.datetime.fromisoformat(r["acceptanceDateTime"][i].replace("Z", "+00:00"))
events.append({
"cik": d["cik"], "accession": r["accessionNumber"][i], "form": form,
"filing_date": r["filingDate"][i], "report_date": r["reportDate"][i],
"accepted_utc": acc_utc.isoformat(),
"accepted_et": acc_utc.astimezone(ZoneInfo("America/New_York")).isoformat(),
"items": [x for x in r["items"][i].split(",") if x],
"primary_doc": r["primaryDocument"][i],
"filed_by_agent": r["accessionNumber"][i][:10] != f'{int(d["cik"]):010d}',
})
Our unified data API design guide shows how to design three tables: events, sources and processing status. For SEC filings, the event key is (CIK, accession). The source table records when you read the submissions file, the index page and each exhibit.
8-K item numbers route events; they do not show importance
Item numbers are the most common filter in filing monitoring products. The SEC Form 8-K lists all items from 1.01 to 9.01. Most items are due within four business days after the event. The Investor.gov guide How to Read an 8-K explains each item type for retail investors.
On our list, the 89 filings had these items. Item 9.01 (financial statements and exhibits) occurred 70 times, and 2.02 (results of operations) 33 times. Item 8.01 (other events) occurred 26 times, 5.02 (officers and directors) 18 times and 7.01 (Regulation FD) 17 times. Each other item appeared one to three times.
Item 9.01 is on almost every 8-K with exhibits. Alone, it is not a signal. The 18 cases of Item 5.02 differ very much in weight. Look at three filings from mid-November:
| Company | 8-K accepted (ET) | Event date | What Item 5.02 says |
|---|---|---|---|
| NVIDIA | 2026-11-12 08:52:41 | 11-11 | The board accepted the resignation of CEO Jensen Huang. CFO Colette Kress became interim CEO. Harvey C. Jones became board chair (source) |
| Home Depot | 2026-11-17 06:08:09 | 11-13 | The CEO ended a medical leave. The board approved a set of leadership changes from November 23 (source) |
| Walmart | 2026-11-16 07:58:13 | 11-13 | The board appointed one new director, who also joined the audit committee (source) |
All three are Item 5.02. A rule engine sees the same number. To separate them, you must read the text. Who left, and who joined?
Is the change immediate? Is it the CEO or a director? A model can do the first classification. But the output must be a candidate, for example: "Candidate: possible CEO change, paragraph 2." The owner then confirms it, and the status changes to "reviewed".
Use fixed fields for the classification. Record the position (CEO, CFO, director, other officer) and the direction (leaves, joins, transition, pay arrangement). Also record the effective date, immediate or not, and the paragraph number in the source.
The NVIDIA filing gives two rows: "CEO, leaves, immediate" and "board chair, joins". The Walmart filing gives "director, joins". The Home Depot filing gives "CEO, transition, effective November 23". The reviewer checks only these fields and does not read the full text again.
Also look at the gap between the event date and the filing date. Of 87 Form 8-K reports on our list, 63 were filed on the event date. The other 24 came one to four business days later, and the longest gap was exactly four business days. The Walmart and Home Depot events happened on Friday, November 13. The companies filed on Monday and on Tuesday.
Attach each 8-K/A to its original. On November 16, AMD filed an 8-K/A with only Item 3.02 (unregistered sales of equity securities). It amends the 8-K of September 28, 2026, which also had only Item 3.02 (event date September 26). The two filings are 49 days apart, and AMD filed an earnings 8-K on November 3, 2026, between them. The accession number does not link an amendment to its original. Look for the original by company, event date and item number. If you cannot find it, mark the amendment "to attach" and do not send it as a new event. If a user already read the summary of the original, send this amendment as a correction on the same card.
Timing: 82 of 87 Form 8-K reports came outside market hours
Users often ask for "real time" monitoring. First, look at when 8-K filings arrive. We converted the acceptance times of the 87 Form 8-K reports to Eastern time and counted them by hour.
The 16:00 hour had 47 filings. The 06:00 hour had 14, and the 08:00 hour had 7. The regular session from 9:30 to 16:00 had only 5. In total, 54 came after 16:00 and 28 came before 9:30.
| Time window (ET) | Form 8-K count | Share | Singapore time (November) |
|---|---|---|---|
| Before 9:30 | 28 | 32% | Before 22:30 the same day |
| 9:30 to 16:00 | 5 | 6% | 22:30 to 05:00 |
| After 16:00 | 54 | 62% | After 05:00 the next day |
For teams in Asia, 16:00 ET is about 05:00 in Singapore, and 06:00 ET is about 19:00 in Singapore. Most "real-time" alerts to a phone arrive at night. A daily summary for the watchlist, plus instant alerts only for events such as CEO changes and deals, fits the work day better.
A team in Singapore can set the daily summary at 11:00 Singapore time. In November, New York uses standard time, so this is 22:00 ET on the previous day. EDGAR stops accepting filings for that day at 22:00. The after-market earnings 8-K filings and late filings, such as the Salesforce filing at 21:02, are all in. The summary then covers the full previous business day.
Trading and quantitative teams have different needs. The 16:00 hour is when most Item 2.02 earnings filings arrive, and these teams need delays of minutes or less. They usually buy the SEC public dissemination service or a market data feed. This article does not cover that use case.
The SEC is careful when it talks about delay. The Webmaster FAQ says that filings are often available on sec.gov within 1 to 3 minutes of the EDGAR timestamp. The delay can increase much under high server load, and the SEC does not guarantee or predict it. For the fastest access, the FAQ points to the Latest Filings search and its RSS feed.
The same FAQ says that the SEC does not offer email alerts for EDGAR filings. It offers dynamic RSS for some searches. Thus the SEC itself does not send free filing alerts by email. Other companies build the alert services on top of RSS or the APIs.
Does the news come before or after the filing? Three 8-K reports
One common reason to monitor SEC filings is "to be faster than the news". We used the EveryInfra Google News API capability google_news/search to test this. Between 16:24 and 16:36 UTC on November 18, 2026 (00:24 to 00:36 Singapore time on November 19), we ran one search for each of three recent 8-K filings. Each search returned 20 stories. We subtracted the 8-K acceptance time from the publish time of each story. The request looks like this:
curl -s https://api.everyinfra.com/api/v1/social \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"platform":"google_news","action":"search",
"params":{"keyword":"Nvidia Jensen Huang resigns Colette Kress interim CEO",
"time_window":"week","language":"en","country":"us"}}'
Each result has these fields: rank, title, url, source, text, published_at, image_url and platform. They agree with the response fields on the Google News API page. The time_window parameter accepts only hour, day, week, month or year. On our first call we sent 7d. The API returned HTTP 422 and did not charge. We changed the value to week and got HTTP 200.
One real google_news/search response, sorted by publish time, with the 8-K acceptance time added. The teal boxes mark the acceptance time and the charge. Captured Nov 19, 2026, Singapore time. EveryInfra API real response, 2026-11-19 00:24:08 SGT
| 8-K | Accepted (UTC) | Stories before filing | Within 60 min after | Later | Earliest story |
|---|---|---|---|---|---|
| NVIDIA Item 5.02 | 11-12 13:52:41 | 1 | 7 | 12 | Fortune, shown 14.7 hours earlier; the story was updated later |
| Home Depot Items 5.02, 7.01 | 11-17 11:08:09 | 4 | 2 | 14 | Two are earnings previews; CNBC 21.6 min earlier; PR Newswire 8.2 min earlier |
| Home Depot Item 2.02 (second 8-K) | 11-17 11:18:03 | 4 | 2 | 14 | Same stories; against this filing, CNBC 31.5 min earlier, PR Newswire 18.1 min earlier |
| Disney Item 2.02 | 11-17 11:30:22 | 4 | 5 | 11 | Three are previews; CNBC shown 6.5 hours earlier |
The board accepted the resignation on November 11. Google News shows a publish time of 23:12 UTC on November 11 for the Fortune story. The date in its URL is also November 11. That is 880 minutes before the 8-K.
But the summary that Google News returns says that the company made the announcement on Thursday, which is November 12. Thus Fortune updated the story after the first version, and we cannot see the first text. We can only say that the media reported the event before EDGAR accepted the filing. We cannot calculate the exact lead.
EDGAR accepted the 8-K at 08:52:41 ET on November 12. Four minutes later, the NVIDIA Newsroom published the company announcement. CNBC followed one minute after that. Within 60 minutes, seven stories appeared. The filing and the company press release came out at almost the same time.
Home Depot shows a different order. The earnings press release on PR Newswire went out at 11:00 UTC. The CNBC story shows 10:46 UTC.
EDGAR accepted the two 8-K filings at 11:08 and 11:18 UTC. The first was the CEO transition (Items 5.02 and 7.01), and the second was the earnings filing (Item 2.02 source). At 11:24 UTC, an aggregator posted "Home Depot filed SEC Form 8-K" (Quantisnow). Its page shows 06:18:03 ET, which is exactly the acceptance time of the earnings 8-K. Google News shows a time six minutes later.
An earnings 8-K under Item 2.02 often furnishes a press release that a wire service already sent. Thus it is usually not first. In the Disney row, one CNBC story shows a time 6.5 hours before the 8-K. We cannot confirm if this is the first publish time or an update time. We report it only as "the time that Google News shows". We do not use it to calculate a lead.
Check the keyword search results too. Each of the three searches returned 20 results. For NVIDIA, all 20 titles mention Huang, Kress or the CEO, from 17 different sources.
For Home Depot, 19 titles include the company name, and 2 of them are previews. The one title without the name is about the earnings of a peer, Lowe's. For Disney, 18 titles include the company name and 3 are previews. Of the two titles without the name, one is about revenue at ESPN, a Disney unit, and one title is only "Document".
A company name filter misses the ESPN story, and a keyword search can add peers. Give each company on the watchlist a set of brand names and officer names. Preview stories before an 8-K are normal. Remove them before you calculate a lead. Otherwise "earnings tomorrow" looks like early knowledge of the earnings. One simple rule: mark titles with "preview", "to report" or "ahead of" as previews and keep them out of the time comparison.
Three filings are a very small sample. They do not show that "SEC filings come after the news". For events such as CEO changes, a monitor matches media reports to the SEC source. It tells the user: "There is now a formal filing, and this is the text." For earnings, the value is to link the press release, the 8-K exhibits and the later 10-Q in one line. Our search and evidence guide says the same thing: find, read the source, and cross-check are three steps. Do not join them into one call.
XBRL helps comparison, but the same number can change concept
In addition to submissions, the SEC public APIs give XBRL data from financial statements. The companyfacts API returns all concepts for one company. The frames API returns all companies that reported one concept, in one unit, for one period. Structured data helps time series and comparison across companies, but only when the concept, unit and period agree.
We read the frames API for calendar Q2 2026 (CY2026Q2) and two revenue concepts. Revenues had 1,669 companies. RevenueFromContractWithCustomerExcludingAssessedTax had 2,307 companies. 437 companies reported both, so the total was 3,539.
| Group (CY2026Q2, USD) | Companies |
|---|---|
| Revenues only | 1,232 |
| RevenueFromContractWithCustomerExcludingAssessedTax only | 1,870 |
| Both concepts, same value | 180 |
| Both concepts, different value | 257 |
| Both concepts, difference over 5% | 176 |
| Total with at least one concept | 3,539 |
Of the 437 companies that reported both concepts, 180 gave the same value and 257 gave different values. For 176 of them, the difference was more than 5%. We did not read the notes of each company to find the cause. One possible cause is that one concept includes other income and the other counts only revenue from contracts with customers. Check a sample of notes before you build a product on it. If you build a revenue ranking from one concept, you miss many companies, or you compare numbers that use different definitions.
One company can also change concept. In the NVIDIA companyfacts file, RevenueFromContractWithCustomerExcludingAssessedTax has only 28 facts. The last quarter for that concept ended on January 26, 2020.
After that, NVIDIA used Revenues. This concept has 280 facts. The latest quarter ended on July 26, 2026, with a value of $96.221 billion, from the 10-Q filed on August 26. A dashboard that uses only the first concept shows "no revenue data" for NVIDIA from 2020 onward, and it gives no error.
| Company | Revenue concept | Facts | Distinct periods | Latest quarter in XBRL |
|---|---|---|---|---|
| Apple | RevenueFromContract… | 120 | 58 | Ended 2026-06-27, 10-Q filed July 31 |
| Walmart | RevenueFromContract… | 120 | 60 | Ended 2026-07-31, 10-Q filed August 28 |
| NVIDIA | Revenues (since 2020) | 280 | — | Ended 2026-07-26, 10-Q filed August 26 |
Apple has 120 facts for only 58 distinct periods, or 2.07 facts per period. The company reports a quarter in its 10-Q, then again as a comparison one year later, and again in the annual report. When you remove duplicates by period, keep the accession and filed date, and use the latest fact. Also keep the older values. Then you can see the difference when a company restates a number.
Units and dimensions can also break a match. The frames API returns only totals without dimensions. Numbers by segment or by region are not in companyfacts either. You must read them by dimension member in the XBRL instance of the 10-Q.
Revenue is usually in USD, earnings per share in USD/shares and share counts in shares. A company sometimes reports a sub-item in a foreign currency. Make the unit part of the key. Two facts are the same only when (concept, unit, period start and end, dimensions) all agree.
There is also a time gap between the 8-K and the XBRL. The NVIDIA press release in the 8-K of November 17 gives revenue of $115.8 billion for the third quarter that ended October 25. But when we read companyfacts on November 19, the latest quarter was still July, at $96.221 billion. The XBRL with an earnings 8-K has only cover page data. Quarterly financial values go into companyfacts when the company files the 10-Q.
If a product shows both the press release number and the XBRL number, label each one with its source and status. For example: "Press release: $115.8 billion (8-K exhibit, not in XBRL yet)". When the 10-Q arrives, replace it with the structured value. A post on a trading forum in October describes the same order (r/HollowPointTrading). First read the press release and exhibits. Then check them against the quarterly report.
Before you compare companies, check the meaning of the concept, the unit and the period. The frames value CY2026Q2 is a calendar quarter. A fiscal quarter can be a few weeks off. In CY2026Q2, NVIDIA has the fiscal quarter that ended July 26, and Apple has the fiscal quarter that ended June 27. When two numbers are not directly comparable, show "not directly comparable" and the reason. Do not convert values silently to fill a chart.
Amendments and later filings join the same event chain
There are many amendments in the full feed. The three daily indexes had 179 to 289 filings with /A, and our watchlist had 69 in 90 days. An 8-K/A amends an 8-K, a 10-K/A amends an annual report, and a SCHEDULE 13G/A updates a holding. Link each amendment to the original. Show which fields and exhibits changed. If a user read or forwarded the old summary, send a correction.
Duplicate removal does not mean that you drop filings on the same topic. A company can disclose an event in an 8-K, add details in a 10-Q and repeat it in the risk factors of the annual report. These are different filing events, but they can share one tracking topic.
The system puts these filings on one timeline under the tracking topic. The NVIDIA CEO change is an example. It has the 8-K on November 12 (Item 5.02) and the interim CEO quote in the earnings release on November 17. The 10-Q will add more later.
| Status | Meaning | Next step |
|---|---|---|
| Machine candidate | A rule or model made the result | Send to the owner for review |
| Reviewed | The owner confirmed the fields | Deliver to the team queue |
| Needs more evidence | Exhibits or XBRL are not complete | Read again when the source updates |
| Corrected | A /A or later filing changed the result | Notify users who saw the old card |
| Invalid | The entity map or class was wrong | Close with the reason |
Give each finding a status: machine candidate, reviewed, needs more evidence, corrected or invalid. Keep "complete" as a separate step. When a new submission appears, the exhibits and the derived data are not always ready at the same time. Your system must be able to update the first, partial snapshot to a full version. It must not keep the first version forever.
"Real time" has two limits: Fair Access and public delay reports
SEC Developer Resources gives the current rule. Each user can send no more than 10 requests per second in total, from any number of machines. The SEC does not allow undeclared bots. Automated requests must declare a User-Agent in the request header.
The SEC first published this limit in an EDGAR rate control notice. The privacy and security page adds that the SEC can limit an IP address for a short time when it goes over the limit. Access returns after the rate stays below the limit for 10 minutes. For this article, we downloaded only about 50 files from the SEC: daily indexes, submissions, frames, companyfacts and a few source documents. That is far from the limit.
Reliable collection uses incremental cursors, conditional requests, a cache and bulk archives. Read the daily index once per day. Read submissions only when Latest Filings or RSS shows a new filing. Refresh companyfacts when a 10-Q or 10-K arrives. Show at least five run states: checked with no relevant event; new event to parse; some exhibits failed; source rate limited; entity map error. Only with these states can a user tell if a quiet day had no new filings or if the monitor did not run.
| Source | What it tells you | Delay | How often to read |
|---|---|---|---|
| Latest Filings RSS | There is a new filing | Shortest | Every few minutes |
| Submissions JSON | All recent filings of one CIK, with all fields | Minutes | When RSS shows a new filing |
| Daily index | All filings of the previous day | One day | Once each morning |
| Companyfacts and frames | Structured financial values | After 10-Q or 10-K | When a periodic report arrives |
Each source has its own job. The Latest Filings RSS feed says "there is something new". It has the shortest delay, but it gives only the title, form type and link.
The submissions JSON says "this company filed these documents". It has all the fields and helps you fill gaps and replay history. The daily index says "these were all filings yesterday". It comes once per day and you use it to find missed filings.
For a list of 30 companies, a typical day looks like this. Read the RSS every few minutes. When a new filing appears, read submissions once or twice and one index page. Read the daily index once the next morning.
The number of reads depends on whether you filter by form at the RSS layer. Without a filter, the list had 10,591 filings in 90 days, about 118 per calendar day, and JPMorgan Chase alone had about 71 per day. A rule "read submissions on each new filing" then runs more than 100 times per day. If you drop 424B2, FWP and 424B3 at the RSS layer, 1,081 filings remain, about 12 per day. If you keep only Form 8-K and Form 4 (89 plus 598), you get about 7.6 per day. All three are far below 10 requests per second. The difference is the volume that you must parse and deduplicate downstream. Sometimes the daily index has a filing from a watchlist company that your event table does not have. Then set that company to "collection error" and replay it.
Reading public filings and submitting filings are two different systems. The API tokens in the EDGAR Next FAQ are for filers who submit documents. They need a Login.gov account and multi-factor authentication. The EDGAR Filer Manual, Volume 1 (version of March 16, 2026) says that EDGAR deactivates each filer API token once per year.
A technical administrator must then log in and confirm it again. The public APIs on data.sec.gov need no key and no token. Keep these two topics separate in your product documents. Then users do not look for an "EDGAR API key" that they do not need.
What public discussion and data APIs can add
SEC filings answer one question: what did the company formally say? Users often also want to know how the market reacts, when the media reported the event, and what employees and customers discuss. This data is on public web pages and in communities, and you can pull it by watchlist with data APIs.
At 16:35 UTC on November 18 (00:35 Singapore time), we used reddit/search from the Reddit API to search for "SEC filing alerts". It returned 9 posts, all from October 5 to 13, 2026. Two were promoted posts from a financial news company for its paid alerts and audio service.
One was a developer post in r/discordbots about an alert bot, with commands such as /filingfilter to filter by form. One was a small-cap research tool in r/qullamaggie. Its author said that he was tired of moving between scanners, SEC filings, news and charts. In an older r/SaaS feedback post, the author planned an alert tool for EDGAR and Indian regulatory filings. One reply said only that it "already exists, many times over", and the author agreed that similar tools exist.
Together, these posts show that "follow a company and get filing alerts" is a crowded category. Form filters, insider trade summaries and news merges are already available.
A new product must go deep into one workflow. Here are two examples. A supplier risk team asks for documents when a company on the list reports a going concern doubt or an auditor change. A sales team gets a reminder when a customer changes its CFO.
| Time (SGT, Nov 19) | Capability | Keyword | HTTP | Results | charged_usd |
|---|---|---|---|---|---|
| 00:24:08 | google_news/search | NVIDIA CEO change | 200 | 20 | 0.000792 |
| 00:25:07 | google_news/search | Home Depot Q3 results | 200 | 20 | 0.000792 |
| 00:35:21 | reddit/search | SEC filing alerts | 200 | 9 | 0.000792 |
| 00:36:16 | google_news/search | Disney Q4 results | 200 | 20 | 0.000792 |
| Total | 0.003168 |
The EveryInfra catalog has these capabilities that fit next to SEC filings. Prices are from the pricing page on November 19, 2026, in USD per 1,000 requests:
| Capability | USD per 1,000 | Use next to filings | Status early on Nov 19 (SGT) |
|---|---|---|---|
google_news/search |
0.792 | Media times and titles around an 8-K | 3 calls, all HTTP 200 |
reddit/search |
0.792 | Retail and practitioner discussion | HTTP 200 |
yahoo_finance/news |
1.389 | News by ticker | HTTP 503, no charge; we used google_news |
yahoo_finance/financials |
1.389 | Financial tables to cross-check XBRL | HTTP 503, no charge |
twitter/search |
0.792 | Fast discussion after an event | HTTP 503 with a retry time, no charge |
EveryInfra does not charge for failed calls or empty results. Each 503 that we got said "Not charged" and gave a retry time in the response. Our guides on self-healing API errors and failure refund reconciliation show how to record each call by request_id. When yahoo_finance/news from the Yahoo Finance API and twitter/search are available again, they can replace the news source in the table. A pull by ticker is more accurate than a pull by keyword.
From alerts to a team workflow
An event card can go into a CRM, a supplier risk list or a research queue. Each team sees the fields that its access allows.
For competitive and sales signals, the card asks the owner whether to update the account plan. For supplier risk, the card can start a request for more documents. For research, the card can hold a hypothesis and counter-evidence.
The NVIDIA card can say: "Item 5.02: CEO resigned; CFO is also interim CEO; effective immediately (8-K 0001045810-26-000082, paragraph 1). Google News already has a story from before the filing (its time can be an update time, so no lead is counted). To review: effect on supplier contracts and the contact list." The system moves public evidence to the right person. It does not replace legal, compliance or investment decisions.
Starter rules for three teams
The same EDGAR data needs different rules for different teams. With our 90-day data for 30 companies, you can estimate how many cards each rule set makes in one quarter. Use these numbers as the expected volume before a pilot.
| Team | Filings to follow | Estimate from 90 days | Question for each card |
|---|---|---|---|
| Supplier risk | 8-K Items 1.01, 1.02, 2.03, 2.04, 4.01, 4.02, 5.02; risk factor changes in 10-K and 10-Q | About 23 item hits (5.02 is 18) | Did contracts, financing, auditors or management change in a way that affects us? |
| Sales and customer success | 8-K Items 5.02 and 2.02; segment revenue in 10-Q | About 51 hits (2.02 is 33) | Who is the new decision maker? Which business line grows or shrinks? |
| Research and competitive intelligence | All 8-K items; Form 4 open market trades; 13G | 89 Form 8-K cards; Form 4 after the code filter | What did the competitor say? What do insiders and large holders do? |
The supplier risk row has the smallest count, but it needs the most accuracy. Item 4.01 (auditor change) and Item 4.02 (prior financial statements can no longer be relied on) did not occur on our list in 90 days. When they occur, someone must act on the same day. This rule set needs a weekly "quiet report" that lists the companies that the monitor checked with no relevant event. Without it, users cannot tell "no events" from "the monitor stopped".
The sales team's cards come in earnings season. Each company files an earnings 8-K once per quarter, 33 in our 90 days. The useful part is the section about the customer's own business, for example a segment or a new region. A model can extract segment numbers from the press release, add one line such as "up or down from last quarter", and link to the source table. The research team needs all 8-K filings and insider activity, so it gets the most cards. Group them into one weekly summary per company.
Changes in the last 60 days that affect data products
- October 19, 2026: the SEC announced a roundtable on machine-understandable data for November 9. The topic was how the public uses machine-understandable data and "Super Intelligence" (SI) tools, with the related risks and costs (press release 2026-106). For you: XBRL and structured disclosure formats can change, so keep your parser flexible.
- November 13, 2026: the SEC proposed changes to executive and director pay disclosure. The rules are in Item 402 of Regulation S-K, which the SEC last reformed fully in 2006. One proposed change limits the named executive officers to the principal executive officer and the principal financial officer (press release 2026-114; Chairman's statement). For you: the structure of pay tables in proxy statements can change, so parsers for the old tables need room to adjust.
- Earlier, on May 5, 2026, the SEC proposed an optional semiannual report on a new Form 10-S. It would replace quarterly 10-Q reports for companies that select it. Such a company files one semiannual report and one annual report each fiscal year, not three quarterly reports and one annual report. The 10-S is due 40 or 45 days after the period, by filer status (press release 2026-42). If the rule passes, "XBRL updates every quarter" is no longer true for some companies. Record the report frequency for each company.
Measure the MVP by the events that people act on
A pilot can cover one user type, a few dozen confirmed CIKs and two or three form types. With our watchlist: 30 companies filed 89 Form 8-K reports in 90 days. One google_news/search and one reddit/search call for each 8-K costs 89 × 2 × $0.000792 ≈ $0.141. That is less than 15 cents per quarter. The SEC submissions and frames APIs are free and have only the 10 requests per second limit. The main cost is people: each review takes a few minutes, and the pilot must measure this time.
First replay a period of history to test duplicate removal, amendments and evidence links. Then start incremental monitoring. Our 90-day replay already tests several things.
Does the system detect a CIK change such as ExxonMobil? Does it put the two 8-K filings after 17:30 on the correct date? Does it attach each 8-K/A to its original? For each event, record if it was relevant, if someone reviewed it, what action it caused and which summaries needed a correction later.
In week one, do one simple thing. Each morning, list the 8-K filings from the previous day for the watchlist in one table. Each row has the acceptance time, item numbers, the model's candidate class and two or three story links.
The owner marks each row as correct or changes the class. After one week, the share of correct rows is the accuracy of the classification. The item type with the most changes shows which rule to fix first.
Use these main metrics. How long does a relevant event take to reach the owner? What causes false alerts and missed events? How long does a review take? Do corrections reach the users who saw the old result?
Which monitoring questions never cause any action? The last metric can mean that the question is not important or that the rule is wrong. Use it in user interviews. The number of downloaded files is not a metric. To start, get a key from the quickstart and run the curl request in this article.
Limits of this approach
Our watchlist has only 30 large companies. Do not apply the results directly to small companies. Their 8-K rhythm, use of filing agents and amendment rate can be very different. The news timing uses only three 8-K filings, with 20 stories each, and it depends on the publish times that Google News shows. Some of these times can be update times. We looked at the two revenue concepts for one quarter only.
We searched Reddit only once. We did not get posts from X, because twitter/search returned 503 that night. The yahoo_finance/news capability for news by ticker also returned 503. We must test these two parts again when the capabilities are available.
The watchlist has no foreign private issuers. They file 6-K and 20-F reports, not 8-K and 10-Q, so they need separate rules. SEC rules, including the 10 requests per second limit, can change. Check them again at launch and during operation. Do not use the numbers in this article as permanent settings.
This article is a design discussion about SEC filing data products. It does not mean that EveryInfra runs an EDGAR monitoring service. It is not investment, legal or compliance advice.
FAQ
Do I need an API key for the EDGAR API?
No, not to read public data. The submissions, companyfacts and frames APIs on data.sec.gov need no key. You must declare a User-Agent in the request header and stay under 10 requests per second (Developer Resources). The API tokens in EDGAR Next are for filers who submit documents. They need a Login.gov account and multi-factor authentication, and a technical administrator must confirm them again each year. A program that only reads public data does not use them.
What is the EDGAR API rate limit?
Each user can send no more than 10 requests per second in total, from any number of machines. If you go over, the SEC can limit your IP for a short time. Access returns after 10 minutes below the limit (privacy and security page). The limit is per user, not per machine. If several machines collect in parallel, they must share one rate budget. For a watchlist, most traffic comes from submissions reads. With a form filter at the RSS layer, a list of 30 companies needs only about 8 to 12 reads per day.
Which time zone does an SEC filing alert use?
In submissions JSON, acceptanceDateTime is in UTC. The filing detail page and the header of the complete submission text file use Eastern time. The filingDate uses a 5:30 p.m. Eastern cutoff, and most filings after that time get the next business day. Forms 3, 4, 5 and 144 and Schedules 13D and 13G, with amendments, keep the same day until 10 p.m. (17 CFR 232.13). Two 8-K filings on our list got a filing date one day later for this reason. The 293 Form 4, 13G and similar filings accepted between 5:30 and 10 p.m. kept their dates. Show both the acceptance time (with a time zone) and the filing date in each alert.
References
- SEC, EDGAR Application Programming Interfaces, https://www.sec.gov/search-filings/edgar-application-programming-interfaces
- SEC, Developer Resources (Fair Access), https://www.sec.gov/about/developer-resources
- SEC, Webmaster Frequently Asked Questions, https://www.sec.gov/about/webmaster-frequently-asked-questions
- SEC, Privacy Information (access rate), https://www.sec.gov/about/privacy-information
- SEC, New rate control limits on EDGAR websites, https://www.sec.gov/filergroup/announcements-old/new-rate-control-limits
- SEC, data.sec.gov public data APIs, https://data.sec.gov/
- SEC, company_tickers.json, read 2026-11-19, https://www.sec.gov/files/company_tickers.json
- SEC EDGAR, daily index form.20261116.idx, 2026-11-16, https://www.sec.gov/Archives/edgar/daily-index/2026/QTR4/form.20261116.idx
- SEC EDGAR, daily index form.20261117.idx, 2026-11-17, https://www.sec.gov/Archives/edgar/daily-index/2026/QTR4/form.20261117.idx
- SEC EDGAR, daily index form.20261113.idx, 2026-11-13, https://www.sec.gov/Archives/edgar/daily-index/2026/QTR4/form.20261113.idx
- SEC, Frequently Asked Questions About Form 13F, https://www.sec.gov/rules-regulations/staff-guidance/frequently-asked-questions-about-form-13f
- SEC, Modernization of Beneficial Ownership Reporting (final rule), 2023-10-10, https://www.sec.gov/files/rules/final/2023/33-11253.pdf
- eCFR, 17 CFR 240.0-3, Filing of material with the Commission, https://www.ecfr.gov/current/title-17/chapter-II/part-240/subpart-A/subject-group-ECFRf2ef38fa463cdfa/section-240.0-3
- SEC, Form 8-K, https://www.sec.gov/files/form8-k.pdf
- SEC Investor.gov, How to Read an 8-K, https://www.sec.gov/investor/pubs/readan8k.pdf
- SEC, Forms 3, 4 and 5, https://www.sec.gov/files/forms-3-4-5.pdf
- eCFR, 17 CFR Part 232 (Regulation S-T), https://www.ecfr.gov/current/title-17/chapter-II/part-232
- Cornell LII, 17 CFR § 232.13 Date of filing, https://www.law.cornell.edu/cfr/text/17/232.13
- SEC, EDGAR Next Frequently Asked Questions, https://www.sec.gov/submit-filings/improving-edgar/edgar-next-improving-filer-access-account-management/edgar-next-frequently-asked-questions
- SEC, EDGAR Filer Manual Volume 1 (v43), 2026-03-16, https://www.sec.gov/files/edgar/filer-information/edgarfm-vol1-v43.pdf
- ExxonMobil Holdings Corporation, Form 8-K12B, 2026-07-01, https://www.sec.gov/Archives/edgar/data/2115436/000119312526291990/d71068d8k12b.htm
- SEC EDGAR, 8-K12B filing detail page 0001193125-26-291990, 2026-07-01, https://www.sec.gov/Archives/edgar/data/2115436/000119312526291990/0001193125-26-291990-index.htm
- Exxon Mobil Corporation, Form 25-NSE, 2026-07-02, https://investor.exxonmobil.com/sec-filings/all-sec-filings/content/0000876661-26-000593/0000876661-26-000593.pdf
- ExxonMobil, ExxonMobil Announces Planned Effective Date for Move to Texas, 2026-06-22, https://investor.exxonmobil.com/company-information/press-releases/detail/1206/exxonmobil-announces-planned-effective-date-for-move-to
- SEC, ExxonMobil Holdings Corp submissions JSON, read 2026-11-19, https://data.sec.gov/submissions/CIK0002115436.json
- SEC, Exxon Mobil Corp submissions JSON, read 2026-11-19, https://data.sec.gov/submissions/CIK0000034088.json
- NVIDIA, Form 8-K (Item 5.02), 2026-11-12, https://www.sec.gov/Archives/edgar/data/1045810/000104581026000082/nvda-20261111.htm
- SEC EDGAR, NVIDIA 8-K filing detail page 0001045810-26-000088, 2026-11-17, https://www.sec.gov/Archives/edgar/data/1045810/000104581026000088/0001045810-26-000088-index.htm
- NVIDIA, NVIDIA Announces Financial Results for Third Quarter Fiscal 2027 (EX-99.1), 2026-11-17, https://www.sec.gov/Archives/edgar/data/1045810/000104581026000088/q3fy27pr.htm
- NVIDIA Newsroom, NVIDIA Announces CEO Transition, 2026-11-12, https://nvidianews.nvidia.com/news/nvidia-announces-ceo-transition
- The Home Depot, Form 8-K (Items 5.02 and 7.01), 2026-11-17, https://www.sec.gov/Archives/edgar/data/354950/000035495026000182/hd-20261113.htm
- The Home Depot, Form 8-K (Item 2.02), 2026-11-17, https://www.sec.gov/Archives/edgar/data/354950/000035495026000184/hd-20261117.htm
- Walmart, Form 8-K (Item 5.02), 2026-11-16, https://www.sec.gov/Archives/edgar/data/104169/000010416926000165/wmt-20261113.htm
- Advanced Micro Devices, Form 8-K/A (Item 3.02), 2026-11-16, https://www.sec.gov/Archives/edgar/data/2488/000119312526462340/d105780d8ka.htm
- SEC, XBRL frames: us-gaap/Revenues/USD/CY2026Q2, read 2026-11-19, https://data.sec.gov/api/xbrl/frames/us-gaap/Revenues/USD/CY2026Q2.json
- SEC, XBRL frames: RevenueFromContractWithCustomerExcludingAssessedTax/USD/CY2026Q2, read 2026-11-19, https://data.sec.gov/api/xbrl/frames/us-gaap/RevenueFromContractWithCustomerExcludingAssessedTax/USD/CY2026Q2.json
- SEC, NVIDIA companyfacts JSON, read 2026-11-19, https://data.sec.gov/api/xbrl/companyfacts/CIK0001045810.json
- SEC, Roundtable on Machine-Understandable Data (press release 2026-106), 2026-10-19, https://www.sec.gov/newsroom/press-releases/2026-106-sec-announces-roundtable-machine-understandable-data-age-super-intelligence
- SEC, Executive and Director Compensation Disclosure Reforms (press release 2026-114), 2026-11-13, https://www.sec.gov/newsroom/press-releases/2026-114-sec-proposes-executive-director-compensation-disclosure-reforms
- SEC, Statement by Chairman Atkins on the executive compensation proposal, 2026-11-13, https://www.sec.gov/newsroom/speeches-statements/atkins-statement-proposing-release-executive-compensation-disclosure-reform-111326
- SEC, Optional Semiannual Reporting proposal (press release 2026-42), 2026-05-05, https://www.sec.gov/newsroom/press-releases/2026-42-sec-proposes-amendments-permit-optional-semiannual-reporting-public-companies
- Fortune, Nvidia's Jensen Huang resigns, CFO Colette Kress named interim CEO, 2026-11-11, https://fortune.com/2026/11/11/nvidia-oust-jensen-huang-spy-affairs/
- CNBC, Nvidia CEO Jensen Huang resigns immediately, 2026-11-12, https://www.cnbc.com/video/2026/11/12/nvidia-ceo-jensen-huang-resigns-colette-kress-appointed-interim-ceo.html
- PR Newswire, The Home Depot Announces Third Quarter Fiscal 2026 Results, 2026-11-17, https://www.prnewswire.com/news-releases/the-home-depot-announces-third-quarter-fiscal-2026-results-updates-fiscal-2026-guidance-302941189.html
- CNBC, Home Depot names Richard McPhail as new CEO, beats earnings expectations, 2026-11-17, https://www.cnbc.com/2026/11/17/home-depot-hd-q3-earnings-2026.html
- Quantisnow, Home Depot Inc. filed SEC Form 8-K, 2026-11-17, https://www.quantisnow.com/insight/home-depot-inc-filed-sec-form-8-k-results-of-operations-6795511
- CNBC, Disney beats fourth-quarter estimates, 2026-11-17, https://www.cnbc.com/2026/11/17/disney-dis-earnings-q-2026.html
- Reddit r/HollowPointTrading, The release is only the start: 8-K versus 10-Q, 2026-10-07, https://www.reddit.com/r/HollowPointTrading/comments/1wzn7am/the_release_is_only_the_start_8k_versus_10q/
- Reddit r/discordbots, I made a Discord bot that DMs you for different events on the stocks you follow, 2026-10-12, https://www.reddit.com/r/discordbots/comments/1x3x7dt/i_made_a_discord_bot_that_dms_you_for_different/
- Reddit r/qullamaggie, Software Sunday: I build a small-cap research tool, 2026-10-08, https://www.reddit.com/r/qullamaggie/comments/1x0k9gc/software_sunday_i_build_a_smallcap_research_tool/
- Reddit r/SaaS, Would your team use a real-time alert system for regulatory filings, https://www.reddit.com/r/SaaS/comments/1l1vnls/feedback_wanted_would_your_team_use_a_realtime/
Originally published on the EveryInfra blog: SEC Filing Monitoring: From EDGAR Updates to Verifiable Events. This article was written with AI assistance; the numbers come from the API calls and sources linked above, and were checked before publishing.
EveryInfra is a pay-per-call data API for AI agents and developers: everyinfra.com.



Top comments (0)