/api/v1/ownership/beneficial-ownership/conversionsList 13G-to-13D and 13D-to-13G filing type conversions.
List 13G-to-13D and 13D-to-13G filing type conversions.
10 tokensSince v3.0.0
Why use this
Surfaces filings where a beneficial owner CONVERTED between 13G (passive) and 13D (active) reporting status — a rare but extremely high-signal event because the conversion is the regulatory moment a filer's PUBLICLY-DECLARED INTENT changed. The 13G→13D direction (`passive_to_active`) is the canonical 'activist campaign launching' indicator: a fund that was reporting passively suddenly switches to active disclosure because they intend to influence management. The reverse direction (`active_to_passive`) often signals the campaign winding down — settlement reached, board seats won, position taking back to passive holding. Each row pairs the prior + current accession so the conversion is observable in one round-trip. The most actionable single endpoint in the 13D/G surface for proxy-fight surveillance.
Common use case
Early detection of passive holders turning activist, or activist campaigns winding down.
Surfaces filings where a beneficial owner converted between 13G (passive) and 13D (active) status — a high-signal event because conversion typically signals an intent shift. Returns the prior + current filings paired so the conversion is observable in one row.
Parameters
| Name | In | Required | Default | Allowed | Description | Example |
|---|---|---|---|---|---|---|
| dateFrom | query | optional | — | — | Inclusive lower bound on `convertedAt` (the date of the conversion-triggering current filing). Format ISO `YYYY-MM-DD`. Use to incrementally poll only new conversions: `dateFrom = last_run_timestamp`. | 2026-01-01 |
| page | query | optional | 1 | — | 1-based page number. Conversions are a small minority of 13D/G corpus (<2%); even broad date ranges typically fit on a single page. | 1 |
| size | query | optional | 50 | — | Page size, capped at 200 server-side. Practical cap matters less here than on the broader filings endpoint because the conversion universe is small. | 50 |
Response schema
| Field | Type | Nullable | Description |
|---|---|---|---|
| conversions | array | no | Array of conversion rows, sorted by `convertedAt DESC` (most recent first). Each row pairs the prior + current filings so the conversion direction and the gap-since-prior are observable in one go. Empty array when no conversions in the date window. |
| conversions[].filerCik | string | no | Filer CIK in 10-char zero-padded form (the entity that converted). Pass to `/ownership/beneficial-ownership/filers/{cik}/portfolio` to see the filer's full position book. |
| conversions[].filerName | string | no | Filer name from the current filing (typically all-caps EDGAR convention). For activist conversions, common high-signal names: `TRIAN FUND MANAGEMENT LP`, `STARBOARD VALUE LP`, `ELLIOTT INVESTMENT MANAGEMENT LP`. |
| conversions[].issuerCik | string | no | Issuer CIK in 10-char zero-padded form (the company being targeted). Pass to `/ownership/beneficial-ownership/issuers/{cik}/summary` for the full beneficial-owner roll-up. |
| conversions[].issuerTicker | string | yes | Resolved issuer ticker (canonical hyphen form). Null only for private-issuer conversions (rare; most M&A target conversions resolve). |
| conversions[].priorFormType | string | no | Form type of the PRIOR filing — `13G` (passive) or `13D` (active). Together with `currentFormType` defines the conversion direction. |
| conversions[].currentFormType | string | no | Form type of the CURRENT filing that triggered the conversion. The interesting cases: `priorFormType=13G AND currentFormType=13D` (passive going active — typical activist campaign launch), `priorFormType=13D AND currentFormType=13G` (active winding down). |
| conversions[].direction | string | no | Conversion direction — literal `"passive_to_active"` (13G→13D, activist campaign launching) or `"active_to_passive"` (13D→13G, campaign winding down). The single most important field on this endpoint — filter on `direction` for direction-specific surveillance. |
| conversions[].priorAccession | string | no | SEC accession of the PRIOR filing. Pass to `/ownership/beneficial-ownership/filings/{accession}` to retrieve the prior filing's full structured payload (purpose, intent flags, exhibits). |
| conversions[].currentAccession | string | no | SEC accession of the CURRENT (conversion-triggering) filing. Pass to `/ownership/beneficial-ownership/filings/{accession}` for the new filing's full payload — typically more interesting than the prior filing since it carries the new declared intent. |
| conversions[].convertedAt | string | no | ISO-8601 UTC timestamp of the CURRENT filing (the moment the conversion was disclosed). The `convertedAt - priorFiledAt` gap is itself a signal — fast conversions (within weeks) suggest a planned escalation; slow conversions (months) suggest opportunistic shifts. |
Sample response
·
- "conversions":
Errors
| Status | Label | Description |
|---|---|---|
| 200 | OK | Request succeeded. |
| 400 | Bad Request | Invalid query, body, or path parameter. |
| 401 | Unauthorized | Missing or invalid Authorization header / api_Token. |
| 402 | Payment Required | Insufficient token balance for this call. Top up |
| 429 | Too Many Requests | Rate limit exceeded for your tier (see /pricing for tier limits). Tier limits |
| 500 | Server Error | Unexpected server-side failure. Retry with backoff; report if persistent. |
Code samples
curl "https://api.finradar.ai/api/v1/ownership/beneficial-ownership/conversions?api_Token=YOUR_API_KEY" \
-H "Authorization: Bearer YOUR_JWT_TOKEN"Generate an API key in /account/credentials to run live queries (literal YOUR_API_KEY placeholder shown until then).