SEC EDGAR · Authentication Profile

Sec Authentication

Authentication

SEC EDGAR secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

Financial DataSECEDGARPublic Company FilingsXBRLRegulatoryGovernmentFinancial ReportingCompany SubmissionsSecurities
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

Filer API Token and User API Token http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/sec-edgar-filer-openapi.yml
summary:
  types:
  - http
schemes:
- name: Filer API Token and User API Token
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: A Filer API Token would be required to be presented to use any of the EDGAR APIs—the
    EDGAR Submission API, EDGAR Submission Status API, and EDGAR Operational Status API. A User
    API Token would be required to be presented for the EDGAR Submission API only. EDGAR submissions
    made using the EDGAR Submission API would be subject to the same authentication and validation
    procedures that apply to submis
  sources:
  - openapi/sec-edgar-filer-openapi.yml