REST API v1

FilingSift API documentation

The stable REST v1 contract exposes issuers, filings, facilities, covenants, comparisons, and evidence-backed events. Public demonstration routes need no key; private or metered access uses a one-time bearer key. Webhooks and MCP are not available.

Base URL and contract

https://api.filingsift.com/api/v1

Schema version 1.0.0 uses JSON envelopes with data and meta. Read the complete OpenAPI 3.1 specification.

Resources

Endpoint	Purpose
`GET /meta`	Version and capability gates
`GET /issuers`	Supported issuers
`GET /filings`	Structured filing summaries
`GET /filings/{accession}`	Complete extraction and provenance
`GET /facilities`	Capacity, draws, and availability
`GET /covenants`	Covenant and legal-event signals
`GET /filing-comparisons`	Comparable-filing changes
`GET /events`	Changes and supported baselines

Filtering, pagination, and caching

List routes accept bounded limit and opaque cursor values plus endpoint-specific ticker, CIK, form, category, verification, filing-date, and effective-date filters. Cursors bind to the filter set and collection snapshot. Public GET responses include strong ETags; authenticated responses are private and never shared-cacheable.

Errors and refusals

HTTP errors return a stable code, message, retryable category, request ID, and schema metadata. Domain refusals are successful records that identify the unresolved concept, reason, evidence, hash, and source locator. Clients must not convert missing or refused values to zero.

Working integrations

JavaScript guide · Python guide · Comparison workflow. Examples use only standard-library or built-in HTTP clients.

Content snapshot: 2026-10-05. Current API data may be newer.