Evaluate 13F API - SEC API for AI

Use this guide for a manager-monitor or research-review workflow built on disclosed Form 13F holdings. A 13F is delayed, periodic manager disclosure. It is not a live portfolio, trade ledger, statement of intent, or complete economic-exposure record.

The buyer job

For one reporting manager, inspect available filings, retrieve a selected report, and compare the latest two parsable reports with their filing context. Direct EDGAR is the better path when you only need the original submission or must choose an arbitrary pair of historical quarters.

Smallest proof of concept

cik identifies the reporting manager, not an issuer held in the report. Start with filing history, then retrieve the selected report, then run the route’s latest-two-parsable-report comparison.

curl --fail-with-body -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/owners/13f/filings?cik=0001067983&limit=20"

curl --fail-with-body -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/owners/13f?cik=0001067983&limit=20"

curl --fail-with-body -X POST -H "x-api-key: $SECAPI_API_KEY" \
  -H "content-type: application/json" --data '{"cik":"0001067983","limit":50}' \
  "https://api.secapi.ai/v1/owners/13f/compare"

The comparison does not accept arbitrary report-date selectors. valueUsdThousands is reported in thousands; make any unit conversion explicit.

What a passing result contains

Retain manager CIK, report date, filing date, accession number, filing URL, returned holdings, request metadata, and provenance/freshness. For the comparison, retain both selected filing dates, row status and deltas. A reviewer must be able to trace an added, removed, or changed row back to both disclosure records.

Source and production limits

The report date is a quarter-end snapshot; the filing date is when it reached the SEC. Keep both.
A missing comparison can mean fewer than two parsable reports. Check filing history before drawing a conclusion.
Amendments, fund structure, corporate actions, and reporting conventions can change a row without a discretionary trade.
Do not describe latest-two-report differences as current holdings, intraperiod trading, or manager intent.
Before monitoring a manager universe, bound the polling schedule and quote the workload through Pricing and limits.

Next decision

Use the comparison only when your product can display its two underlying reports and label the result as a filing difference. For an arbitrary historical comparison, retrieve the intended reports separately and own that comparison policy.

13F API reference

Inspect selected-report semantics.

13F tutorial

Design an idempotent monitor.

Price the monitor

Estimate repeated manager coverage.

Create an API key

Start a selected-manager proof.

Open the sandbox

Inspect report and comparison shapes.

Public pricing

Review monitoring options.

Inspect available reports

Use the manager CIK and retain filing dates.

Compare evidence

Keep both report identities beside the diff.

Bound monitoring

Set cadence before covering a manager universe.

​The buyer job

​Smallest proof of concept

​What a passing result contains

​Source and production limits

​Next decision