Financial Datasets — Get beneficial ownership

Retrieve beneficial-ownership stakes (SEC Schedules 13D and 13G: holders of more than 5% of a class of shares), one row per reporting person with the Financial Datasets API. The request accepts a pagination cursor when provided. Use it to validate or enrich records in a contact workflow. The GET request schema also lists ticker, filer_cik, type.

Selected price
$0.02 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Optional parameters (11)
The ticker symbol of the subject company. Provide ticker or filer_cik, not both.
The SEC CIK of the filer (the beneficial owner). Provide ticker or filer_cik, not both. Use the /beneficial-ownership/filers endpoint to look up CIKs by owner name.
Filter by stake type: activist (Schedule 13D) or passive (Schedule 13G).
When true, returns the full amendment history of each stake instead of only its current state.
Filter by exact filing date in YYYY-MM-DD format.
Filter by filing date greater than or equal to this date (YYYY-MM-DD).
Filter by filing date less than or equal to this date (YYYY-MM-DD).
Filter by filing date greater than this date (YYYY-MM-DD).
Filter by filing date less than this date (YYYY-MM-DD).
The total number of rows to return (default: 10; no maximum). This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.
Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.

Sample response

No response example is configured. A real response is available only after running the API, or when a published sample is added.

Response result

Response structure

No response structure is available yet. Run a request to inspect its response.

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Financial Datasets — Get beneficial ownership with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.