Name: SEC Event Intelligence API
Brand: data-apis-1
SKU: api-data-apis-1-sec-event-intelligence
Availability: InStock
Author: API Market

# SEC Event Intelligence API

SEC Event Intelligence API provides structured JSON access to public SEC EDGAR filing activity for product teams, research tools, compliance workflows, and automation systems. It is designed for developers who need practical filing-change monitoring without building and maintaining a separate EDGAR ingestion pipeline.

The API focuses on workflow-ready SEC filing data: latest filings, filing changes since a date, multi-company watchlist polling, company lookup, company profiles, company filing history, company event feeds, insider filing metadata, and accession-number filing summaries. Responses are JSON-first and are intended for backend jobs, dashboards, alert workers, CRM enrichment, spreadsheet workflows, and internal data products.

This is data infrastructure only. It returns public SEC filing metadata and source-linked records. It does not provide investment advice, ratings, recommendations, buy or sell signals, legal advice, tax advice, compliance certification, or personalized financial guidance.

## Common use cases

- Monitor a watchlist of tickers for newly observed SEC filings.
- Poll for 8-K, 10-Q, 10-K, S-1, 13D, 13G, Form 3, Form 4, and Form 5 activity.
- Resolve company names, tickers, and CIKs before requesting filing feeds.
- Enrich research dashboards with recent filing events and company-level coverage metadata.
- Build alert workers that route filing changes into Slack, email, CRM, spreadsheets, or internal databases.
- Review public insider filing metadata by ticker.
- Fetch a filing summary by accession number for downstream review queues.
- Replace manual EDGAR browsing with scheduled, machine-readable JSON checks.

## Core endpoints

- GET /health — service health and ingest freshness.
- GET /demo — public no-key sample response for evaluating response shape.
- GET /v1/sec/latest — latest normalized SEC filing records.
- GET /v1/sec/changes — filing-change feed for polling jobs.
- GET /v1/sec/watchlist/changes — multi-company watchlist change feed.
- GET /v1/sec/companies/search — ticker, company name, and CIK lookup.
- GET /v1/sec/company/{ticker}/profile — company profile and local filing coverage.
- GET /v1/sec/company/{ticker}/filings — company filing history by ticker.
- GET /v1/sec/company/{ticker}/events — normalized company event feed.
- GET /v1/sec/insider-trades — public Forms 3, 4, and 5 metadata by ticker.
- GET /v1/sec/forms/{accessionNo}/summary — source-linked filing summary lookup.

## Authentication

Call this API through the API.market proxy after subscribing to a plan. Use the API key generated in your API.market account and send it with the `x-api-market-key` header.

Base URL:

```text
https://prod.api.market/api/v1/data-apis-1/sec-event-intelligence
```

Required headers:

```text
x-api-market-key: YOUR_API_KEY
Accept: application/json
```

Keep API.market credentials server-side and do not embed keys in public frontend code.

## Quick cURL examples

Health check:

```bash
curl -X GET "https://prod.api.market/api/v1/data-apis-1/sec-event-intelligence/health" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Accept: application/json"
```

Public demo response:

```bash
curl -X GET "https://prod.api.market/api/v1/data-apis-1/sec-event-intelligence/demo" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Accept: application/json"
```

Latest 8-K filings:

```bash
curl -X GET "https://prod.api.market/api/v1/data-apis-1/sec-event-intelligence/v1/sec/latest?form=8-K&limit=25" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Accept: application/json"
```

Watchlist changes for multiple companies:

```bash
curl -X GET "https://prod.api.market/api/v1/data-apis-1/sec-event-intelligence/v1/sec/watchlist/changes?tickers=AAPL,MSFT,NVDA&since=2026-07-01&limit=25" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Accept: application/json"
```

Company search:

```bash
curl -X GET "https://prod.api.market/api/v1/data-apis-1/sec-event-intelligence/v1/sec/companies/search?q=apple&limit=10" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Accept: application/json"
```

Company filing history:

```bash
curl -X GET "https://prod.api.market/api/v1/data-apis-1/sec-event-intelligence/v1/sec/company/AAPL/filings?limit=25" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Accept: application/json"
```

Form 4 insider filing metadata:

```bash
curl -X GET "https://prod.api.market/api/v1/data-apis-1/sec-event-intelligence/v1/sec/insider-trades?ticker=MSFT&limit=25" \
  -H "x-api-market-key: YOUR_API_KEY" \
  -H "Accept: application/json"
```

## Watchlist workflow

The watchlist endpoint is the best first production endpoint for most buyer workflows. Send a comma-separated list of tickers or CIKs and a since date. The response groups changes by watched company and includes counts plus filing records, so it can be used directly in polling jobs and alert workers.

Recommended flow:

1. Resolve company names or tickers with /v1/sec/companies/search.
2. Save the ticker or CIK list in your application.
3. Poll /v1/sec/watchlist/changes with a since date.
4. Store returned accession numbers or filing URLs to avoid duplicate alerts.
5. Send new records to your workflow destination.

Example request:

    GET /v1/sec/watchlist/changes?tickers=AAPL,MSFT,NVDA&since=2026-07-01&limit=25

## Filing-change workflow

Use /v1/sec/changes when your application needs a general filing-change feed rather than a fixed watchlist. Common filters include since, ticker, form, eventType, and limit.

Example request:

    GET /v1/sec/changes?since=2026-07-01&form=8-K&limit=50

This is useful for current-report monitors, regulatory workflow queues, company research pipelines, and internal filing dashboards.

## Company lookup workflow

Use /v1/sec/companies/search before polling when users enter free-form company names. The endpoint can support ticker lookup, CIK lookup, and company-name search.

Example request:

    GET /v1/sec/companies/search?q=apple&limit=10

After resolving the company, call company profile, company filings, company events, or watchlist changes.

## Response shape

Responses are JSON objects with data and meta fields where appropriate. Records are designed for automation and may include company identifiers, ticker or CIK references, SEC form type, accession number, filing date, observed timestamp, source links, and normalized event fields depending on the endpoint.

Public demo responses are available without a key so buyers can inspect the response shape before subscribing. Production data endpoints require API authentication.

## MCP and Postman evaluation

The product also exposes public documentation and evaluation assets outside the API.market listing:

- Documentation: https://api.data-apis.com/docs
- OpenAPI schema: https://api.data-apis.com/openapi.json
- Public demo: https://api.data-apis.com/demo
- Postman collection: https://api.data-apis.com/postman
- MCP setup: https://api.data-apis.com/mcp

Use Postman when a team wants a shared request workspace before moving credentials into a backend service. Use the MCP path when a remote MCP-capable client needs no-key setup checks and production hosted MCP access.

## Data and compliance notes

SEC Event Intelligence API is built from public SEC EDGAR filing information and related normalized metadata. It is intended for monitoring, research, and workflow automation. Buyers remain responsible for validating filings against official SEC sources, handling compliance requirements, and making final business, legal, or investment decisions.

The service does not provide investment advice, recommendations, ratings, trading signals, legal advice, tax advice, or compliance certification. It is a developer-facing data API for public filing infrastructure.

SEC EDGAR filing-change, latest filings, company search, watchlist monitoring, and filing summary API for investor research and compliance workflows.