SEC Data API

Simple self-service pricing

Every plan uses the same SEC endpoints, provenance fields, and shared account API key. Paid plans increase request capacity; they do not hide core data behind a second contract.

Upgrade, downgrade, payment methods, and cancellation are managed through the shared Grizzly Bulls account. Usage already consumed in the current UTC month carries across plan changes.

More than an EDGAR proxy

SEC.gov remains the upstream authority. Grizzly Bulls maintains the acquisition, retention, parsing, normalization, temporal, and API layers that production applications otherwise have to build themselves. Customer requests are served from retained or reviewed state and never trigger a request to SEC.gov.

Current developer surface

The OpenAPI document is the machine-readable authority for request and response schemas. Inspect the OpenAPI 3.1 contract →

Make your first request

1. Create or sign in to a Grizzly Bulls account.
2. Open Developer APIs and generate the shared account API key.
3. Keep the key server-side and send it as an Authorization: Bearer header.

curl --fail-with-body -H "Authorization: Bearer $GRIZZLY_BULLS_API_KEY" "https://grizzlybulls.com/api/v1/sec/filings?form=10-K&limit=3"

const response = await fetch(
  "https://grizzlybulls.com/api/v1/sec/filings?form=10-K&limit=3",
  { headers: { Authorization: "Bearer " + process.env.GRIZZLY_BULLS_API_KEY } },
);

if (!response.ok) throw new Error("SEC API request failed: " + response.status);
const payload = await response.json();
console.log(payload.data.filings);

import json
import os
import urllib.request

request = urllib.request.Request(
    "https://grizzlybulls.com/api/v1/sec/filings?form=10-K&limit=3",
    headers={"Authorization": f"Bearer {os.environ['GRIZZLY_BULLS_API_KEY']}"},
)

with urllib.request.urlopen(request) as response:
    payload = json.load(response)

print(payload["data"]["filings"])

Try the API in your browser

Paste the shared API key from your account and run any GET path from the OpenAPI contract. The explorer keeps the key only in component memory and never includes the key or request path in analytics events.

Higher-value workflows

curl --fail-with-body -H "Authorization: Bearer $GRIZZLY_BULLS_API_KEY" "https://grizzlybulls.com/api/v1/sec/companies/CIK/financials?period=annual&asOf=2026-01-15T00%3A00%3A00.000Z&limit=25"

curl --fail-with-body -H "Authorization: Bearer $GRIZZLY_BULLS_API_KEY" "https://grizzlybulls.com/api/v1/sec/filings/ACCESSION_NUMBER/institutional-holdings?limit=100&offset=0"

curl --fail-with-body -H "Authorization: Bearer $GRIZZLY_BULLS_API_KEY" "https://grizzlybulls.com/api/v1/sec/filing-diff?from=ACCESSION_NUMBER&to=ACCESSION_NUMBER"

Semantics that stay visible

• Source authority: SEC filings and structured SEC sources remain upstream evidence; Grizzly Bulls responses are retained or reviewed projections of that evidence.
• No request-time scraping: customer traffic never proxies through to SEC.gov.
• Time: filing date, report period, observation time, source availability, and retrieval time remain distinct where the underlying contract needs them.
• 13F: reported issuer name and CUSIP remain source observations in the accession-scoped holdings endpoint; the API does not pretend every row is a canonical Grizzly Bulls company security.
• Corrections over guesses: missing or unsafe retained state fails closed rather than being silently inferred.