SEC Filings Scraper for 10-K and 10-Q Data
SEC EDGAR is a public source, yet a dependable filing pipeline still has to retrieve each page, run any client-side JavaScript, cope with throttling, and convert the result into fields your application can persist.
This page explains a hosted rendering and extraction approach for that task: the caller provides a filing URL together with extraction logic, and structured output is returned. The approach suits teams that would prefer not to run their own browser infrastructure and proxy pool; it does not replace EDGAR's own index or your financial analysis. The capability descriptions below are conditional on the operating terms of the service you use. Verify the current parameter set, credit costs, trial terms and pricing with the service operator before depending on them in production.
Three ways teams use SEC filing data
Filing workflows differ in which parts of a filing record they actually consume, so it is worth deciding up front which fields your pipeline needs to store and which it can ignore. The three patterns below are common, and each one leans on a different subset of the available fields. The field list itself is a technical fact; the guidance about which fields matter for each workflow is a practical recommendation, not a rule imposed by the source data. Treat the field choices as a starting point to adapt to your own storage and analysis requirements, and confirm any service-specific behavior with the operator before relying on it in production.
What the scraper reads from an SEC filing
Each SEC EDGAR filing returns a consistent field set: filing type, filer name, CIK, accession number, period of report, filing date, document URLs and an exhibit list. That covers the identity and location of a filing; the financial numbers inside the document are a separate extraction step, which is where AI extraction rules or CSS/XPath rules come in.
Use the field map below as a checklist before you build storage:
| Field | Use in a pipeline |
|---|---|
| Filing type | Route 10-K, 10-Q and 8-K records to different parsers |
| Filer name | Human-readable label for dashboards |
| CIK | Stable company identifier across filings |
| Accession number | Unique filing handle for deduplication and audit |
| Period of report | Align financial periods across companies |
| Filing date | Sort and monitor new filings |
| Document URLs | Re-fetch the primary document and exhibits |
| Exhibit list | Locate supporting agreements and disclosures |
If two records share an accession number, treat them as the same filing and reconcile rather than append.
Request controls and what each one changes
A documented request takes an SEC filing URL plus optional parameters. The controls most relevant to filing work are: render_js, which runs the page in a real headless browser and returns post-render HTML, useful when the filing page depends on client-side JavaScript; stealth_proxy, which routes the request through a stealthier proxy path, useful when a target becomes aggressive about automated traffic; country_code, which routes through a residential IP in the chosen country, useful only when content genuinely varies by geography, since EDGAR itself is a US public source; ai_extract_rules, which accepts a natural-language extraction specification and returns structured JSON without selectors; and CSS/XPath extraction rules, which target exact elements when you already know the page structure. A common mistake is enabling every control at once, since each adds cost or latency. Start with the plain request, add render_js only if the returned HTML lacks the fields, and add stealth_proxy only if you observe blocking. Confirm the current parameter set and credit costs with the service operator before relying on them in production.
Worked example: one filing URL to one record
Suppose your watchlist contains a company whose latest annual report is at an EDGAR URL. You send that URL with your API key and, if needed, render_js=true. The response you act on contains the filing type, filer name, CIK, accession number, period of report, filing date, document URLs and exhibit list.
Your pipeline then does three things:
- Deduplicate on accession number so a re-run does not create a second record.
- Store the document URLs alongside the parsed fields so an analyst can open the source.
- Optionally pass ai_extract_rules to pull specific figures from the document body into a second JSON object.
This example uses a generic filing URL and the field list above; it does not assert a real company's figures.
Three failure modes and how to tell them apart
Not every failed request means the same thing. Distinguish these before changing configuration:
- Concurrency limit reached. The API enforces concurrency limits per plan, not per-target rate limits. If requests queue or reject while other targets work, check your plan's concurrent request allowance.
- Target throttling. The filing source may throttle aggressive request patterns. Space out requests or use multiple sessions.
- Anti-bot blocking. If responses look like challenge pages rather than filings, enable stealth_proxy on the request.
A useful diagnostic order: confirm the URL returns a filing in a normal browser, then send the plain API request, then add render_js, then add stealth_proxy. Change one variable at a time so you know which control fixed the problem.
Setup path
A typical setup sequence is: register for an account to obtain an API key and any trial credits the operator makes available; choose a client library for your stack (Python, Node, Go, PHP or Ruby) or send requests directly with cURL; send the SEC filing URL together with your API key; then add advanced parameters only where the plain request falls short. The dashboard request builder can produce a snippet in those languages before you commit code to your repository. Working code samples exist per language. Test in the request builder first, then move the generated snippet into your codebase. If a first-party SDK is offered, use its documented package name; otherwise send the documented HTTP request directly. Trial availability and terms are determined by the service operator; check the signup page for the current conditions.
Plan and credit context
The service publishes tiered plans with monthly API credits and concurrent request allowances. Credit consumption depends on the controls you enable: a plain request starts at one credit, JavaScript rendering costs more, and premium proxies cost more again. The validity period of credits is determined by the service operator and should be confirmed before purchase. Because plan prices and allowances change, verify current figures on the pricing page before committing a budget. The plan comparison table on this page is a dated reference, not a quotation. Current plan names, prices and allowances are set by the service operator and should be confirmed against the operator's current pricing page.
| Plan | Monthly price | API credits | Concurrent requests | JS rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
This table is a dated reference to plans published by the source publisher, not an offer by this site. Tax treatment of listed prices and the validity period of credits are determined by the service operator and should be confirmed before purchase. Requests begin at 1 credit each; JavaScript rendering and premium proxies consume additional credits. Plan names, prices, credit allowances, concurrency limits and feature inclusions change over time, so verify current figures on the operator's pricing page before committing a budget.
Frequently asked questions
How do I start scraping SEC filings?
Register for an account to obtain an API key and whatever trial credits the operator makes available. Then issue a GET request containing the SEC filing URL. Under the documented behavior, the page is rendered, proxies are rotated, and the resulting data is returned. If trial credits are offered, use them to test before choosing a plan. Trial availability and terms are determined by the service operator; check the signup page for the current conditions.
Will I get blocked when scraping SEC filings?
The service rotates residential proxies and uses a real headless browser, so requests resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request.
Can I scrape SEC filings without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. You can also use n8n workflows for filing monitoring.
How do I handle JavaScript when scraping SEC filings?
Pass render_js=true on the request. The page runs in a real headless browser, JavaScript executes server-side, and you receive the post-render HTML.
Can I scrape SEC filings from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography, though EDGAR itself is a US public source.
What's the rate limit for scraping SEC filings?
The service has concurrency limits per plan, not per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.
Do I need to parse the filing document myself?
The API returns filing metadata and document URLs. To pull specific figures from inside a document, use ai_extract_rules with a natural-language specification or CSS/XPath extraction rules against the document page.
Can I get SEC filings as Markdown for an LLM?
Yes. Filing pages can be returned as clean Markdown, ready to feed into an LLM for summarization or due-diligence workflows.