/api/v1/indexGet daily Master Index.
Get daily Master Index.
1 tokensSince v1.0.0
Why use this
The cheapest billed endpoint (1 token) — returns the daily SEC EDGAR master-index for a given date as a flat list of accession numbers + CIKs + form types + acceptance timestamps. Mirrors EDGAR's daily index format (which itself mirrors SEC's `daily-index/full-index/YYYY/QTRn/master.YYYYMMDD.idx` files) but normalized to JSON or CSV and cached for 60 seconds. The right endpoint for: building a local mirror of SEC filings (sync workflows that walk dates sequentially), audit-trail reconciliation, and high-frequency polling cursors that don't want to burn quota. Cheaper than `/api/v1/sec/filings` because it's a flat-list lookup against the daily-index table — no full filtering / pagination machinery.
Common use case
Syncing a local database with the SEC's daily output for complete coverage.
Returns the daily filing index — a flat, deterministic list of accession numbers accepted on a given date, sorted by acceptance time. Mirrors EDGAR's daily index format but normalized to JSON and cached for 60 seconds. Cheapest billed endpoint (1 token) so customers can use this as a polling cursor without burning quota.
Parameters
| Name | In | Required | Default | Allowed | Description | Example |
|---|---|---|---|---|---|---|
| date | query | required | — | — | ISO `YYYY-MM-DD` date for which to retrieve the master-index. Returns 404 for future dates and dates before SEC EDGAR's electronic-filing era (1993). Note: weekends + federal holidays return empty `accessions` arrays (SEC doesn't accept filings on those days) — your sync code should handle this without erroring. | 2026-01-15 |
| format | query | optional | json | — | Output format — `json` (default; structured response with `date` + `accessions[]` + `count`) or `csv` (newline-delimited rows: `accession_number,cik,form_type,accepted_at`). Use CSV for streaming to file or piping to Postgres `\COPY`; use JSON for in-process consumption. | json |
Response schema
| Field | Type | Nullable | Description |
|---|---|---|---|
| date | string | no | ISO `YYYY-MM-DD` date echoed back. Useful for asserting your client's date construction (timezone bugs are common — confirm against this echo). |
| accessions | array | no | Array of accession-row entries for filings accepted on the requested date, sorted by `accepted_at ASC` (chronological — earliest filings first). Empty array on weekends, federal holidays, and dates outside SEC coverage (NOT 404 — clients should treat empty as 'no filings that day' not as an error). |
| accessions[].accession_number | string | no | SEC accession number in canonical `XXXXXXXXXX-YY-NNNNNN` format. Pass to `/api/v1/sec/filings/{accession_number}` for full filing detail or to the form-type-specific drill-down endpoints. |
| accessions[].cik | string | no | Filer CIK in 10-character zero-padded form. The stable identifier for joining against subsequent filing-detail or ownership queries. |
| accessions[].form_type | string | no | Canonical SEC form type (e.g. `4`, `13F-HR`, `8-K`, `10-K`, `S-1`, `13D/A`). Use to filter the per-day list to the form types your sync pipeline cares about — Form 4 is the highest-volume entry on most days (~80% of weekday filings). |
| accessions[].accepted_at | string | no | ISO-8601 UTC timestamp of SEC EDGAR's acceptance moment. Use for intra-day ordering — ET market-hours filings cluster around 09:00-21:00 ET; overnight is quiet (10pm-6am ET no new filings). Expected total range matches the requested calendar date in ET. |
| count | integer | no | Total accession count for the date — matches `accessions.length`. Useful for top-level audit metrics ('SEC accepted X filings yesterday'). Typical values: weekdays 5K-50K (off-season vs filing-season); weekends and holidays 0. |
Sample response
·
- "date": "2026-05-01"
- "accessions":
- "count": 1
Errors
| Status | Label | Description |
|---|---|---|
| 200 | OK | Request succeeded. |
| 400 | Bad Request | Invalid query, body, or path parameter. |
| 401 | Unauthorized | Missing or invalid Authorization header / api_Token. |
| 402 | Payment Required | Insufficient token balance for this call. Top up |
| 429 | Too Many Requests | Rate limit exceeded for your tier (see /pricing for tier limits). Tier limits |
| 500 | Server Error | Unexpected server-side failure. Retry with backoff; report if persistent. |
Code samples
curl "https://api.finradar.ai/api/v1/index?api_Token=YOUR_API_KEY" \
-H "Authorization: Bearer YOUR_JWT_TOKEN"Generate an API key in /account/credentials to run live queries (literal YOUR_API_KEY placeholder shown until then).