Insiders - Yellowbrick

GET /api/v1/insiders fuzzy-searches Form 4 reporting owners by name. It is the same ranking as the in-app insider combobox. Use it when you know a name (or part of one) and need a cik to pass as filter.reportingOwnerCik on Insider Trades → Search. See also the Filters guide.

Request

GET /api/v1/insiders?q=buffett&limit=10
Authorization: Bearer cw_...

Parameter	Required	Default	Notes
`q`	Yes	—	Name query. Trimmed. Must be non-empty.
`limit`	No	`20`	Max results. 1–50.

Missing or empty q returns 400.

Response

{
  "data": [
    {
      "cik": "1253718",
      "name": "BUFFETT HOWARD",
      "latestTicker": "LNN",
      "numTickers": 1
    }
  ]
}

Field	Type	Notes
`cik`	string	Reporting-owner CIK. Pass this as `filter.reportingOwnerCik` on trade search.
`name`	string	Name as stored on the reporting-owner record.
`latestTicker`	string \| null	Most recent ticker associated with this insider, if any.
`numTickers`	number \| null	Distinct tickers associated with this insider.

Results are ranked best-match first. An empty data array means no matches.

How matching works

Query is matched against reporting owner names (not tickers or company names).
Matching is fuzzy: word-level edit distance, prefix/suffix matches, and trigram similarity (same logic as the product combobox).
Order of name parts is flexible (warren buffett and buffett warren both work).
This endpoint does not search trades. It only resolves owners.

Use the CIK on trade search

{
  "filter": {
    "reportingOwnerCik": "1253718",
    "filingDatePreset": "1 year",
    "sortBy": "filedAt",
    "sortDirection": "desc"
  },
  "pagination": {
    "cursor": null,
    "pageSize": 50
  }
}

reportingOwnerCik is an exact match. Always take cik from this endpoint (or another trusted source)—do not invent CIKs from the name string.

Errors

Status	When
`400`	Missing/invalid `q` or `limit`
`401`	Missing or invalid API key
`403`	Premium required