Python example
SEC Company Lookup Resolver
A resolver pattern for products that start with customer-entered company names, tickers, or CIKs and need normalized issuer metadata before calling filing-change or watchlist endpoints.
GET /v1/sec/companies/search?q=apple&limit=10
import os
import requests
API_HOST = "https://sec-event-intelligence.p.rapidapi.com"
HEADERS = {
"x-rapidapi-host": "sec-event-intelligence.p.rapidapi.com",
"x-rapidapi-key": os.environ["RAPIDAPI_KEY"],
}
search = requests.get(
f"{API_HOST}/v1/sec/companies/search",
headers=HEADERS,
params={"q": "apple", "limit": 10},
timeout=20,
)
search.raise_for_status()
for company in search.json()["data"]:
profile = requests.get(
f"{API_HOST}/v1/sec/company/{company['ticker']}/profile",
headers=HEADERS,
timeout=20,
)
profile.raise_for_status()
print(company["ticker"], company["cik"], profile.json()["data"]["filingCount"])
Implementation Steps
This example is designed for self-serve evaluation before a buyer subscribes or imports generated snippets from RapidAPI.
- Accept a company name, ticker, or CIK from the buyer workflow.
- Call company search to normalize the ticker and CIK before filing requests.
- Fetch the company profile when the UI needs coverage counts or recent filing context.
Endpoints Used
The recipe stays inside the live SEC Event Intelligence product surface so it can be tested immediately.
GET /v1/sec/companies/searchGET /v1/sec/company/{ticker}/profileGET /v1/sec/watchlist/changes
Example FAQ
Can this resolve company names before watchlist polling?
Yes. Use company search first, then pass the resolved ticker into watchlist or filing-change endpoints.
Does this return private company identifiers?
No. It returns public SEC issuer metadata available from the live product database.