List second-degree connections

GET /api/v1/connections/second-degree

People connected to one of your own first-degree contacts, but whom you don't know directly. Each entry names the bridging connector, so you can see who could make the introduction. Requires a user-scoped MCP token — organization API keys are rejected with 403.

Coverage is bounded

Second-degree networks can be very large, so this endpoint returns a bounded window rather than the whole set: your warmest first-degree contacts, and the warmest connections through each.

That means totalCount is the number of distinct people found in the returned window, not the size of your entire second-degree network. Two fields tell you where you stand:

• scannedBridges — how many of your first-degree contacts were considered.
• capped — true when the scan hit its limit, so more of your network exists beyond these results.

Passing viaConnectorId scopes the scan to a single connector and is the fastest way to answer "who can this contact introduce me to?". The per-connector edge cap still applies, so check capped even when this parameter is set.

Query parameters

Example

curl -H "Authorization: Bearer $TOKEN" \"https://app.usehomie.com/api/v1/connections/second-degree?limit=10"

Response

{
  "data": {
    "connections": [
      {
        "id": "person_...",
        "name": "Alex Johnson",
        "linkedinId": "alexjohnson",
        "position": "VP Engineering",
        "currentCompany": "Stripe",
        "warmness": 71,
        "viaConnector": { "id": "person_...", "name": "Maria Silva" }
      }
    ],
    "totalCount": 4820,
    "returnedCount": 10,
    "limit": 10,
    "offset": 0,
    "nextOffset": 10,
    "hasMore": true,
    "scannedBridges": 200,
    "capped": true
  }
}

Results are ordered warmest first. warmness is the score on the connector→person edge (absent when that edge hasn't been scored yet). People you already know directly are excluded — they're first-degree, so use List connections for those.