API overview
Public REST API for querying your Homie network.
The app labels connection strength Relationship. API and MCP responses retain their existing warmness, warmnessBreakdown, and related field names; the terminology change does not change their values or contracts.
The Homie API gives your apps and scripts read access to your organization's network: warm intro paths, people, companies, and search.
Base URL
https://app.usehomie.com/api/v1All endpoints accept and return JSON. Bodies must use Content-Type: application/json for POST requests.
Authentication
Send an organization API key as a Bearer token on every request:
curl -H "Authorization: Bearer homie_sk_..." \https://app.usehomie.com/api/v1/search/people?q=alexSee Authentication to generate a key. Endpoints scoped to one user's personal network require a user-scoped MCP OAuth token instead; the endpoint reference calls this out where it applies.
Response shape
Successful responses return JSON with a data field. Some search endpoints also include pagination fields or a meta object:
{
"data": [ ... ],
"meta": { "searchTerms": ["..."] }
}Errors return { error: string, code?: string } with an appropriate status code. See Errors.
Every response includes a Homie-Request-Id header. Include it when reporting issues.
OpenAPI spec
The full spec is served at:
GET https://app.usehomie.com/api/v1/openapi.jsonImport it into Postman, Insomnia, or use it to generate clients with openapi-typescript, oapi-codegen, etc.
Usage
Public API rate limits are not enforced yet. Keep automated calls reasonable; quota headers and 429 responses will be documented when limits are added.