List a person's network

GET /api/v1/people/network

The people a given person is connected to: their reach, warmest first. This is the endpoint for "who does this person know?", "who could they introduce us to?", or "show me warm paths out of their network".

Identify the person with whichever handle you hold: name, linkedinId, or personId. Names are matched loosely, and the best-connected match wins a tie.

The person has to be in your organization's network: one of your members, or someone a member is directly connected to. Anyone else returns 403.

Always read `coverage` first

How complete a person's network is in Homie is a different question from how big it is, and coverage is the only thing that tells you which you're looking at:

synced: the person has a Homie account and their own connections were imported. The list is their network.
derived: the connections were observed indirectly, through the people around them. This is the slice Homie can see, not the whole thing.
none: Homie has no connections for them at all.

Most people are derived or none. When coverage is none the empty list means "this network isn't mapped", never "this person knows nobody". Don't report it as the latter.

Already-requested introductions

People your organization has already asked for an introduction to are left out by default and counted in excludedIntroRequested, so an existing conversation isn't proposed twice. Pass includeIntroRequested=true to get them back, each annotated with introRequested and introStatus.

Query parameters

Name	Type	Required	Description
`name`	string	one of these three	The person's name, matched loosely.
`linkedinId`	string	one of these three	Their LinkedIn handle.
`personId`	string	one of these three	Their Homie person id.
`limit`	number	no	1-50, default 20.
`offset`	number	no	0-based offset. Pass the previous response's `nextOffset`.
`includeIntroRequested`	`"true"` \| `"false"`	no	Default `"false"`. Pass the literal string `"true"` to include people you've already requested an intro to.

Example

curl -H "Authorization: Bearer $TOKEN" \"https://app.usehomie.com/api/v1/people/network?name=Maria%20Silva&limit=10"

Response

{
  "data": {
    "person": {
      "id": "person_...",
      "name": "Maria Silva",
      "linkedinId": "mariasilva",
      "position": "Head of Partnerships",
      "currentCompany": "Stripe"
    },
    "connections": [
      {
        "id": "person_...",
        "name": "Alex Johnson",
        "position": "VP Engineering",
        "currentCompany": "Figma",
        "city": "Helsinki",
        "country": "Finland",
        "warmness": 68,
        "warmnessSignals": ["Worked together at Stripe", "4 mutual connections"]
      }
    ],
    "totalCount": 412,
    "returnedCount": 10,
    "limit": 10,
    "offset": 0,
    "nextOffset": 10,
    "hasMore": true,
    "excludedIntroRequested": 2,
    "coverage": "synced"
  }
}

warmness is the score on the edge from this person to that connection, and warmnessSignals says in words why they're close. Warmness measures how reachable someone is, not whether they're worth reaching, so pair this with your ICP to keep only real prospects.