Event Filings

Discover event filings by ticker, CIK, date range, form type, or query.

When To Use It

Use these tools to discover filings, inspect filing artifacts, and retrieve source-backed document evidence.

Request Examples

BASE_URL="${EDGAR_API_URL:-https://www.edgarparser.com}"
 
curl -sS -G "$BASE_URL/api/filings/events" \
  -H "Authorization: Bearer $EDGAR_API_KEY" \
  --data-urlencode "ticker=AAPL" \
  --data-urlencode "form_types=8-K,10-K" \
  --data-urlencode "query=revenue recognition"

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",
  "form_types": [
    "8-K",
    "10-K"
  ],
  "query": "revenue recognition"
}
 
response = requests.get(f"{base_url}/api/filings/events", headers=headers, params=params, timeout=30)
response.raise_for_status()
data = response.json()

Response Fields To Inspect

• accession, filing_url, form type, and period fields to confirm the filing identity.
• Pagination or truncation fields before assuming the returned text is complete.
• Section titles and document names when citing prose back to the filing.

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

Filings, Filing Document, Filing Sections

Generated Reference

Contract

Parameters

Response Schema (200)

{}