# FilingWire

> Two independent data APIs built from SEC EDGAR filings: the Funding API (Form D private
> fundraising) and the Risk API (classified 8-K material corporate events). Business-level
> records only, every row linked to its source filing on sec.gov. Operated from Quebec,
> Canada.

Freshness is DAILY, not real-time: EDGAR's own index is published daily, so nothing here
is intraday and we never describe it as such. Form D is checked several times a day.

## What each product is

- [Risk API](https://filingwire.io/hub/risks): every event-bearing 8-K, classified into bankruptcy,
  restructuring and layoffs, delisting risk, mergers and acquisitions, executive
  departures and appointments, debt acceleration, restatements, auditor changes, cyber
  incidents and contract changes. The event type is read from the filing's own item codes
  on about 95% of records; a filing whose only item is the 8.01 catch-all is classified by
  a model or stays `other`. Severity is a model-assigned TRIAGE score and is explicitly
  not investment, legal or compliance advice.
- [Funding API](https://filingwire.io/hub/funding): every Form D filing, parsed from the filing XML with
  no language model at all: issuer, amount sold, offering amount, industry group, state,
  investor count, minimum investment, security types, exemption. Pooled investment funds
  are excluded. There is no ticker field, because only about 4% of Form D issuers have one.

## Limits worth repeating accurately

- About a third of 8-K events carry the `other` event type. On a 400-row sample that is
  dividends, NAV notices, shareholder meetings and buybacks, not hidden distress. A caller
  filtering only the named types will not see those rows.
- Form D issuers are private companies: about 42% self-select "Other" or "Other Technology"
  as their industry group, and they file no SIC code. That is a property of the form.
- No personal data in any structured field on either product. The one exception is the 8-K
  `summary`, which quotes the filing, so an executive-departure summary can name the
  executive who left. That text is verbatim from a public SEC filing.
- There is no alerting, no webhook delivery and no uptime SLA on any tier.

## Access

- [Free API key](https://filingwire.io/free): 1,000 requests a month, one key for both products, no card.
  The key is emailed. List endpoints on the free tier return the most recent 30 days;
  single-company and single-filing lookups return full history on every plan.
- [Pricing](https://filingwire.io/pricing): paid tiers lift the 30-day window. Checkout is on this site.
- [Quickstart](https://filingwire.io/quickstart): base URLs, the auth header, one call in curl, Python
  and JavaScript, the response envelope, and the error codes.
- [Playground](https://filingwire.io/playground): runs a real query against either product and shows the
  actual JSON response, including the 8-K summary text. No key and no signup needed to
  read it, and it is the fastest way to see the record shape before writing any code.
- Send the key as the `X-API-Key` header. Both products are also listed on RapidAPI, where
  a key issued there is sent as `X-RapidAPI-Key` through their proxy instead.

## Machine-readable

- OpenAPI (Risk): https://filingwire.io/risks/openapi.json
- OpenAPI (Funding): https://filingwire.io/funding/openapi.json
- Live coverage and freshness: https://filingwire.io/risks/v1/meta and https://filingwire.io/funding/v1/meta. These are
  the authoritative row counts and last-ingest timestamps; this file deliberately states
  no corpus size, because a number written here would go stale.

## If the question is how to do it yourself

EDGAR is free and needs no key, and these guides describe working with it directly rather
than through us. They are the honest answer when somebody asks whether they need a vendor
at all, and they carry the traps that cost us a night each.

- [Parse Form D with Python](https://filingwire.io/guides/parse-form-d-python): the XML paths, and why
  summing `totalAmountSold` double counts.
- [Read 8-K item codes](https://filingwire.io/guides/8-k-item-codes-python): the header carries titles
  rather than numbers, and the submission file is unbounded.
- [EDGAR rate limits](https://filingwire.io/guides/edgar-rate-limits): ten requests a second across every
  sec.gov host, the mandatory User-Agent, and why a pinned date range still shifts.
- [Ticker to CIK](https://filingwire.io/guides/ticker-to-cik): the published map, and why the relation is
  many-to-one.

## Optional

- [Use cases](https://filingwire.io/use-cases): the same two products described by the job they do, one
  page per job, each with the exact request.
- [How it works](https://filingwire.io/how-it-works): the ingestion and classification pipeline.
- [Status](https://filingwire.io/status): the ingest run log, per product.
- [About](https://filingwire.io/about): what the corpus covers and what it excludes.
- [Terms](https://filingwire.io/terms) and [Privacy](https://filingwire.io/privacy).