Skip to main content
Use this guide to move one production read from sec-api.io to SEC API. SEC API provides issuer resolution, filing retrieval, sections, and reported facts through its documented REST API. Do not assume similarly named endpoints have identical contracts.

​
Pick one user job

Start with a low-risk workflow that has a clear pass or fail result. The public API reference defines supported parameters and fields. A successful response for one issuer or form is evidence for that bounded case, not a coverage claim.

​
Verify identity before downstream output

For each matched filing, compare ticker, CIK, form, filing date, accession number, and source URL before comparing extracted text or values. Store the request parameters, retrieval time, requestId, and available provenance, freshness, materialization, or warning fields.

​
Dual-run the exact retrieval you need

Test your actual filing families, exhibits, historical window, and rendering needs. SEC API may be a good fit for a documented filing-and-section workflow. Keep your existing provider or direct EDGAR path where it better serves an unqualified requirement.

​
Cut over one reversible read

  1. Use x-api-key for machine credentials and keep it out of URLs and browser bundles.
  2. Dual-run a defined issuer and form set.
  3. Compare source identity, pagination, nullability, and units as well as business fields.
  4. Honor Retry-After for 429; do not retry a failure until its condition changes.
  5. Release one path behind a reversible control and retain a secret-free request record.

​
Next step

Promote only the read that passes your recorded acceptance test. Then repeat the process for the next workflow rather than treating a single cutover as platform-wide parity.

Filing API reference

Review routes and response fields.

API conventions

Apply authentication, pagination, and retry rules.

Error catalog

Interpret a failed dual run.