Filing Tables

Return filing table metadata or one hydrated structured table.

When To Use It

Use these tools when the answer depends on tables embedded in filing documents rather than normalized XBRL facts.

Request Examples

BASE_URL="${EDGAR_API_URL:-https://www.edgarparser.com}"
 
curl -sS -G "$BASE_URL/api/tables" \
  -H "Authorization: Bearer $EDGAR_API_KEY" \
  --data-urlencode "ticker=AAPL" \
  --data-urlencode "year=2025" \
  --data-urlencode "quarter=4"

import os
import requests
 
base_url = os.getenv("EDGAR_API_URL", "https://www.edgarparser.com")
headers = {"Authorization": f"Bearer {os.environ['EDGAR_API_KEY']}"}
params = {
  "ticker": "AAPL",
  "year": 2025,
  "quarter": 4
}
 
response = requests.get(f"{base_url}/api/tables", headers=headers, params=params, timeout=30)
response.raise_for_status()
data = response.json()

Response Fields To Inspect

• table_id, title, section, and accession before using a table as evidence.
• Row labels, column labels, units, and footnotes instead of inferring meaning from position alone.
• Pagination or match-score fields when search returns multiple candidate tables.

Errors And Coverage

• 401 or 403: the API key is missing, expired, or not allowed to use this tier.
• 429: retry after the rate-limit window, and prefer broader batch or series tools over repeated single-period calls.
• Cold work can take longer and may queue background fetch or parse work; use status fields or follow-up tools before finalizing.
• Honor pagination and truncation metadata; request the next page instead of assuming the first response is complete.

Related Tools

Search Filing Tables, Compare Filing Tables, Filing Sections

Generated Reference

Contract

Parameters

Response Schema (200)

{
  "additionalProperties": true,
  "type": "object"
}