.ai domains. Marketing routes such as /api-docs, /developer, and /documentation redirect to https://docs.getintrod.ai.
Authentication
Session and OAuth entry points for login, LinkedIn, Google, and email verification workflows.
Graph APIs
Warm-path, TrustRank, and graph-backed route families that drive relationship intelligence.
People & companies
Search and lookup endpoints for people, companies, and network-driven discovery workflows.
Generated inventories
Route and environment inventories generated directly from the repository so the docs stay grounded.
Make your first call
Start with the public health surface. It is the safest way to verify that the API domain is reachable before moving into session-scoped product APIs.Base surfaces
| Surface | Base URL | Notes |
|---|---|---|
| Public health | https://api.getintrod.ai/health/* | Safe for liveness, readiness, and operational checks |
| Browser-session APIs | https://api.getintrod.ai/api/* | Primary product surface for dashboard-authenticated flows |
| Extension APIs | https://api.getintrod.ai/api/extension/* | Chrome extension sync and pairing contract |
| Dashboard bridge routes | https://api.getintrod.ai/api/dashboard/* | Server-to-server flows used by the dashboard |
Auth model
- Public
- Session
- Bridge
Health probes such as
/health/live, /health/ready, and /health/status do not require a product session.Key route families
| Area | Routes |
|---|---|
| Health | /health/live, /health/ready, /health/status |
| Extension sync | /api/extension, /api/extension/v1/linkedin/sync/* |
| Dashboard bridge | /api/dashboard/* |
| Graph intelligence | /api/graph/* |
| People and network search | /api/people/*, /api/network/* |
| Introduction workflows | /api/dashboard/*, /api/intros-ai/* |
| Integrations | /api/integrations/*, /api/enrich/*, /api/calendar/*, /api/crm/* |
Authentication and scope
Most product APIs require an authenticated user session. Extension sync APIs must remain user-scoped because sync payloads contain relationship data and imported LinkedIn contact context.Reference tracks
- Authentication
- Graph APIs
- People APIs
- Company APIs
- Intro APIs
- Generated endpoint inventory
- Generated environment variables
Public API reference status
The current Express API does not yet publish a complete OpenAPI specification. Until that exists, keep manual API docs focused on stable route families, operational semantics, and the graph/pathfinding contract. When OpenAPI generation is added, configure Mintlify’sapi.openapi setting in docs.json and add generated reference pages under this group.