/api/v1/ownership/holders/{uuid}Get holder detail with alternate CIKs and cross-system flags.
Get holder detail with alternate CIKs and cross-system flags.
5 tokensSince v3.0.0
Why use this
Full profile of a unified holder by UUID — includes alternate CIKs (multi-CIK holders post-merger), name aliases (former names + DBAs), cross-system filing-volume metadata (per-regime counts + first/last filing dates), and the same `is_insider/is_institutional/is_beneficial_owner` flags surfaced by the search endpoint. The natural detail-page backend after a [GET /api/v1/ownership/holders](/docs/ownership-and-positions/unified-holders/get-ownership-holders) search palette resolves a UUID. Pair with [GET /api/v1/ownership/holders/{uuid}/filing-history](/docs/ownership-and-positions/unified-holders/get-ownership-holders-uuid-filing-history) for the filing timeline view.
Common use case
Building a comprehensive holder-profile page (e.g. `/holders/{uuid}`) with all CIKs, name aliases, filing-volume metadata, and cross-system flags. Also useful for verifying that the Phase 47 linker has correctly clustered identities — if an expected alternate CIK is missing from `alternate_ciks[]`, the linker may need a manual override (rare; <0.5% of holders).
Full unified-holder profile by UUID. Includes alternate CIKs (rare; multi-CIK post-merger holders), name aliases (former names + DBAs — Facebook -> Meta Platforms appears here), per-regime filing counts (Form 4 / 13F / 13D-G), and the same cross-system flags surfaced by the search endpoint. The natural detail-page backend for /holders/{uuid} profile pages. The Phase 47 holder-linker uses deterministic (canonical_cik, normalized_name) clustering — UUIDs are stable across re-runs for the same cluster so they're safe to persist client-side. For the chronological filing-feed view of the same holder use GET /api/v1/ownership/holders/{uuid}/filing-history; for position-by-issuer drill-downs use GET /api/v1/ownership/positions/{holder_uuid}/issuer/{issuer_cik}; for cross-source filing rollups grouped by source-type use GET /api/v1/ownership/cross-reference/{holder_uuid}.
Parameters
| Name | In | Required | Default | Allowed | Description | Example |
|---|---|---|---|---|---|---|
| uuid | path | required | — | — | Holder UUID — the stable Phase-47 identifier. Look up via [GET /api/v1/ownership/holders](/docs/ownership-and-positions/unified-holders/get-ownership-holders) (`q` or `cik` search). UUIDs are deterministic across linker re-runs for the same `(canonical_cik, normalized_name)` cluster, so they're safe to persist client-side. Returns 404 on unknown UUIDs. | 7f1a2b30-c4d5-46e7-9f01-23456789abcd |
Response schema
| Field | Type | Nullable | Description |
|---|---|---|---|
| holder_uuid | string | no | Echoed UUID identifier. |
| name | string | no | Canonical holder name. |
| type | string | no | Primary classification — `individual` / `institution` / `group`. |
| primary_cik | string | yes | Primary 10-character zero-padded SEC CIK (the canonical CIK chosen by the linker; typically the most-filed CIK across all regimes). Null on holders identified by name-only. |
| alternate_ciks | array | no | Array of alternate 10-char zero-padded CIKs the same holder has used across filings. Multi-CIK holders are uncommon (post-merger institutions, holding-company-vs-subsidiary distinctions, or 13F-filer-vs-Section-16-filer CIK splits). Empty array for the typical single-CIK holder. |
| name_aliases | array | no | Array of historical name variants the holder has filed under (former names, DBAs, post-rebrand identifiers). E.g. Facebook -> Meta Platforms appears here as `["FACEBOOK INC", "META PLATFORMS INC"]`. Useful for surfacing 'formerly known as' on profile pages. |
| is_insider | boolean | no | `true` when the holder has filed Form 3/4/5. |
| is_institutional | boolean | no | `true` when the holder has filed 13F-HR/NT. |
| is_beneficial_owner | boolean | no | `true` when the holder has filed Schedule 13D/G. |
| filing_counts | object | no | Per-regime filing counts: `{ form_4: integer, form_13f: integer, form_13dg: integer }`. Useful for activity-level visualization on profile pages (e.g. donut chart of filing-type distribution). |
| first_filing_at | string | yes | ISO-8601 UTC timestamp of the holder's earliest known filing across all three regimes. Null on rare holders with empty filing history. |
| last_filing_at | string | yes | ISO-8601 UTC timestamp of the holder's most-recent filing. Useful for sorting profile pages by recency or surfacing 'last seen' on dashboards. |
Sample response
·
- "holder_uuid": "7f1a2b30-c4d5-46e7-9f01-23456789abcd"
- "name": "BERKSHIRE HATHAWAY INC"
- "type": "institution"
- "primary_cik": "0001067983"
- "alternate_ciks": []
- "name_aliases":
- "BERKSHIRE HATHAWAY INC"
- "is_insider": false
- "is_institutional": true
- "is_beneficial_owner": true
- "filing_counts":
- "form_4": 0
- "form_13f": 102
- "form_13dg": 8
- "first_filing_at": "1999-11-15T17:00:00Z"
- "last_filing_at": "2026-04-15T20:14:32Z"
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/holders/{uuid}?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).