Skip to main content
GET
Get a company’s metadata and a bounded orbit of people. The path value can be a FreshTalent company key, an exact company name, or a LinkedIn company URL containing the value. URL-encode names or URLs before placing them in the path. The response contains up to 40 current people and up to 40 leavers. These arrays are not paginated and are not guaranteed to contain every person at the company. Each person row has the full Person field shape but only the two most recent/current positions are hydrated. See Person response shapes.
string
required
Company key, exact company name, or a LinkedIn company URL. The Gateway decodes the path value before lookup.
company.name and company.linkedin_url can be null. current_count and alum_count are graph counts and can be larger than the returned arrays. role_mix maps each non-null recorded role family to its relationship count. current includes current positions; leavers includes people with an ended, non-current position. Counts and returned arrays use different predicates: alum_count includes an explicitly non-current position or any recorded end date, while leavers requires both a normalized end date and is_current: false. A person with multiple stints can qualify for both current and alumni groups.

Response schema

Errors and recovery

  • 404 not_found: no visible company matched the decoded key, exact name, or LinkedIn URL fragment. Search first with Search companies, then retry with the returned key.
  • 401 unauthorized: provide a valid API key in Authorization: Bearer ....
  • 402 payment_required: restore active organization access.
  • 5xx or a transient network failure: retry this read with bounded backoff, jitter, and a timeout.
  • 429: retry this idempotent GET with exponential backoff and jitter after slowing down. The shared Gateway limit is 300 requests per minute per client IP as the Gateway sees it. Honor Retry-After; see Rate limits.
See Errors for the common error envelope. There is no pagination cursor for the orbit arrays; use Search people with a company filter when you need a separately paged people result.

Next steps

Create a company Target with POST /targets and { "input": "Anduril", "kind": "company" } to monitor the company network.