Skip to main content
Use this page to make one small production request before you build a larger workflow. Resolve a company first, confirm the returned identity, then use that identity to retrieve a filing, statement, or search result.
These examples call the production API and can count against the authenticated organization’s usage. Keep the shown limits while you validate response shapes, then inspect billing and limits before a repeated workload.

Set an API key

Create an account at secapi.ai/signup, create an API key in the signed-in dashboard, and expose it only to the process making the request.
Send the key in x-api-key. Do not put it in browser code, a checked-in file, or an Authorization: Bearer header. API keys, usage, and billing explains the boundary between machine credentials and dashboard actions.

Resolve a company

This request resolves Apple and returns its canonical CIK and identity metadata. Keep the request ID with your logs.
Confirm that the response includes ticker, cik, name, and requestId. The entity resolution reference documents accepted identifiers and response fields.

Retrieve a filing after identity is confirmed

Keep accessionNumber, filingDate, filingUrl, and requestId with anything derived from the filing. The latest filing reference documents filters and response fields.

Choose the next request

Read a filing section

Add a source-backed filing section to the issuer workflow.

Retrieve statements

Check annual and quarterly statement routes and constraints.

Price a repeated job

Inspect limits and quote the real paths before scaling.
Read API conventions before adding pagination, version pinning, or retry logic. Read troubleshooting when a request returns an error.