SEC Filings returns the recent EDGAR filing history for a US public company by ticker - 10-K annual reports, 10-Q quarterlies, 8-K current reports, Form 4 insider filings, S-1 registrations and more - each with its filing date, form type and a direct link to the document, plus derived filing-activity analytics calculated for you.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// SEC Filings response payload
}
}
About the SEC Filings API
SEC Filings works by projecting the SEC EDGAR submissions feed for US public companies into a clean, decision-ready filing history. On top of the raw filing list it derives activity analytics - counts by form type, filing cadence, and days since the last annual, quarterly and current report - so you can see a company's disclosure activity at a glance rather than paging through EDGAR. Data is refreshed continuously from official SEC filings.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use SEC Filings
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the SEC Filings API do?
How do I authenticate SEC Filings API requests?
How much does the SEC Filings API cost?
How fast is the SEC Filings API?
What response formats does the SEC Filings API support?
What HTTP method does the SEC Filings API use?
Request parameters — GET /v1/secfilings
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
tickerRequired | string | AAPL | Stock ticker symbol (e.g. AAPL, MSFT, ADBE) length 1-6 |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
formOptionalPremium | string | 10-K | Filter to a single form type (e.g. 10-K, 10-Q, 8-K, 4). |
limitOptionalPremium | integer | 10 | Number of filings to return (1-50). Defaults to 5. range 1-50 |
curl "https://api.apiverve.com/v1/secfilings?ticker=AAPL&form=10-K&limit=10" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/secfilings
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"ticker": "AAPL",
"cik": "0000320193",
"company": "Apple Inc.",
"sic": "3571",
"sicDescription": "Electronic Computers",
"fiscalYearEnd": "0927",
"totalRecentFilings": 1000,
"count": 4,
"latest": {
"annual": {
"form": "10-K",
"filingDate": "2025-11-01",
"accessionNumber": "0000320193-25-000123",
"primaryDocument": "aapl-20250927.htm",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000123/aapl-20250927.htm",
"daysAgo": 62
},
"quarterly": {
"form": "10-Q",
"filingDate": "2025-08-01",
"accessionNumber": "0000320193-25-000106",
"primaryDocument": "aapl-20250628.htm",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000106/aapl-20250628.htm",
"daysAgo": 154
},
"currentReport": {
"form": "8-K",
"filingDate": "2025-10-30",
"accessionNumber": "0000320193-25-000121",
"primaryDocument": "aapl-20251030.htm",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000121/aapl-20251030.htm",
"daysAgo": 64
}
},
"filings": [
{
"form": "10-K",
"filingDate": "2025-11-01",
"reportDate": "2025-09-27",
"primaryDocDescription": "10-K",
"accessionNumber": "0000320193-25-000123",
"primaryDocument": "aapl-20250927.htm",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000123/aapl-20250927.htm",
"items": null,
"isXBRL": true
},
{
"form": "8-K",
"filingDate": "2025-10-30",
"reportDate": "2025-10-30",
"primaryDocDescription": "8-K",
"accessionNumber": "0000320193-25-000121",
"primaryDocument": "aapl-20251030.htm",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000121/aapl-20251030.htm",
"items": "2.02,9.01",
"isXBRL": true
},
{
"form": "4",
"filingDate": "2025-10-16",
"reportDate": "2025-10-14",
"primaryDocDescription": "FORM 4",
"accessionNumber": "0000320193-25-000118",
"primaryDocument": "xslF345X05/wf-form4.xml",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000118/xslF345X05/wf-form4.xml",
"items": null,
"isXBRL": false
},
{
"form": "10-Q",
"filingDate": "2025-08-01",
"reportDate": "2025-06-28",
"primaryDocDescription": "10-Q",
"accessionNumber": "0000320193-25-000106",
"primaryDocument": "aapl-20250628.htm",
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000106/aapl-20250628.htm",
"items": null,
"isXBRL": true
}
],
"analytics": {
"formCounts": {
"3": 22,
"4": 512,
"8-K": 96,
"10-Q": 84,
"10-K": 28,
"DEF 14A": 27,
"SC 13G": 41
},
"filingsLast30Days": 3,
"filingsLast90Days": 9,
"filingsLast365Days": 74,
"daysSinceLastFiling": 62,
"daysSinceLastAnnual": 62,
"daysSinceLastQuarterly": 154,
"averageDaysBetweenFilings": 12.4,
"mostActiveForm": "4"
}
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
ticker | string | "AAPL" | Stock ticker symbol for the company |
cik | string | "0000320193" | SEC Central Index Key unique identifier |
company | string | "Apple Inc." | Official registered name of the company |
sic | string | "3571" | Standard Industrial Classification code |
sicDescription | string | "Electronic Computers" | Industry description for the SIC code |
fiscalYearEnd | string | "0927" | Fiscal year end in MMDD format |
totalRecentFilings | number | 1000 | Total filings in the company's recent EDGAR feed |
count | number | 4 | Number of filings returned in this response |
latest | object | {...} | Most recent filing of each headline type |
annualPremium | object | {...} | Most recent 10-K annual report |
formPremium | string | "10-K" | Form type (10-K) |
filingDatePremium | string | "2025-11-01" | Date the annual report was filed |
accessionNumberPremium | string | "0000320193-25-000123" | SEC accession number for the filing |
primaryDocumentPremium | string | "aapl-20250927.htm" | Primary document filename |
urlPremium | string | "https://www.sec.gov/Archives/edgar/data/320193/000032019325000123/aapl-20250927.htm" | Direct link to the filing document |
daysAgoPremium | number | 62 | Days since the annual report was filed |
quarterlyPremium | object | {...} | Most recent 10-Q quarterly report |
formPremium | string | "10-Q" | Form type (10-Q) |
filingDatePremium | string | "2025-08-01" | Date the quarterly report was filed |
accessionNumberPremium | string | "0000320193-25-000106" | SEC accession number for the filing |
primaryDocumentPremium | string | "aapl-20250628.htm" | Primary document filename |
urlPremium | string | "https://www.sec.gov/Archives/edgar/data/320193/000032019325000106/aapl-20250628.htm" | Direct link to the filing document |
daysAgoPremium | number | 154 | Days since the quarterly report was filed |
currentReportPremium | object | {...} | Most recent 8-K current report |
formPremium | string | "8-K" | Form type (8-K) |
filingDatePremium | string | "2025-10-30" | Date the current report was filed |
accessionNumberPremium | string | "0000320193-25-000121" | SEC accession number for the filing |
primaryDocumentPremium | string | "aapl-20251030.htm" | Primary document filename |
urlPremium | string | "https://www.sec.gov/Archives/edgar/data/320193/000032019325000121/aapl-20251030.htm" | Direct link to the filing document |
daysAgoPremium | number | 64 | Days since the current report was filed |
filings | array[4] | Recent filings, most recent first | |
form | string | "10-K" | SEC form type (10-K, 10-Q, 8-K, 4, ...) |
filingDate | string | "2025-11-01" | Date the filing was submitted |
reportDate | string | "2025-09-27" | Period or event date the filing reports on |
primaryDocDescription | string | "10-K" | Description of the primary document |
accessionNumber | string | "0000320193-25-000123" | SEC accession number for the filing |
primaryDocument | string | "aapl-20250927.htm" | Primary document filename |
url | string | "https://www.sec.gov/Archives/edgar/data/320193/000032019325000123/aapl-20250927.htm" | Direct link to the filing document |
items | object | null | 8-K item numbers disclosed, when applicable |
isXBRL | boolean | true | Whether the filing includes XBRL structured data |
analytics | object | {...} | |
formCountsPremium | object | {...} | Count of filings by form type in the recent feed |
3Premium | number | 22 | |
4Premium | number | 512 | |
8-KPremium | number | 96 | |
10-QPremium | number | 84 | |
10-KPremium | number | 28 | |
DEF 14APremium | number | 27 | |
SC 13GPremium | number | 41 | |
filingsLast30DaysPremium | number | 3 | Number of filings in the last 30 days |
filingsLast90DaysPremium | number | 9 | Number of filings in the last 90 days |
filingsLast365DaysPremium | number | 74 | Number of filings in the last 365 days |
daysSinceLastFilingPremium | number | 62 | Days since the most recent filing of any type |
daysSinceLastAnnualPremium | number | 62 | Days since the most recent 10-K |
daysSinceLastQuarterlyPremium | number | 154 | Days since the most recent 10-Q |
averageDaysBetweenFilingsPremium | number | 12.4 | Average days between recent filings |
mostActiveFormPremium | string | "4" | Most frequently filed form type |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 6 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | SEC Filings calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 33 | Free |
| Starter | $29.99 | 200,000 | 33,333 | $0.90 |
| Pro | $99.99 | 1,000,000 | 166,666 | $0.60 |
| Mega | $299.99 | 4,000,000 | 666,666 | $0.45 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/secfilings
No SDK to install — this is a plain HTTPS call to /v1/secfilings with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/secfilings" \
-H "x-api-key: YOUR_API_KEY"Resources
Call it from Node.js — GET /v1/secfilings
No SDK to install — this is a plain HTTPS call to /v1/secfilings with your key in the x-api-key header. Swap in a real key and it runs as-is.
const res = await fetch("https://api.apiverve.com/v1/secfilings", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Call it from Python — GET /v1/secfilings
No SDK to install — this is a plain HTTPS call to /v1/secfilings with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/secfilings",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Call it from C# / .NET — GET /v1/secfilings
No SDK to install — this is a plain HTTPS call to /v1/secfilings with your key in the x-api-key header. Swap in a real key and it runs as-is.
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/secfilings");
Console.WriteLine(json);Resources
Call it from Go — GET /v1/secfilings
No SDK to install — this is a plain HTTPS call to /v1/secfilings with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/secfilings", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Call it from PHP — GET /v1/secfilings
No SDK to install — this is a plain HTTPS call to /v1/secfilings with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/secfilings");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Call it from Ruby — GET /v1/secfilings
No SDK to install — this is a plain HTTPS call to /v1/secfilings with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/secfilings")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Zero-code embed — one snippet, no backend
Drop an interactive SEC Filings form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — SEC Filings API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the SEC Filings API.
Finance
- Balance Sheet
- Benchmark Rate
- BIN Lookup
- Bitcoin Price
- Cash Flow Statement
- Company Lookup
- Cost of Living
- CPI Inflation
- Currency Converter
- Currency Symbols
- Dividends
- Earnings Report
- Ethereum Price
- Exchange Rate
- Financial Ratios
- GDP Data
- Global Stock Market
- Gold Price
- I-Bond Rates
- IFSC Lookup
- Income Statement
- Income Tax Brackets
- Income Tax Calculator
- Inflation Rate
- Insider Trading
- Interest Rate
- Jobs Report
- Loan Calculator
- Minimum Wage
- Mortgage Calculator
- Mortgage Rate
- National Debt
- Palladium Price
- Platinum Price
- Population Data
- Purchasing Power
- Routing Number Lookup
- Sales Tax Calculator
- Sales Tax Lookup
- Sanctions Screening
- SEC Filings
- Silver Price
- Stock Exchange
- Stock Market Open Times
- SWIFT Code Lookup
- Trade Balance
- Treasury Yields
- Unemployment Rate
- VAT Rates
Related articles
All articles →
Enrich Your CRM with Public Company DataAutomatically fill in company details for sales leads using SEC data. Ticker, industry, address, and more from a single API call.Read
Currency Conversion: Handling Exchange Rates CorrectlyExchange rates change constantly. Learn how to handle currency conversion in applications with accuracy and reliability.Read
Going Global: Building Multi-Currency AppsYour app works great in dollars. Now a customer in Germany wants to pay in euros. Here's what to know.Read