Welcome to Voyager

Voyager is the LinkedIn automation layer for AI agents. 252 REST endpoints across Voyager and Sales Navigator, a Model Context Protocol (MCP) server with 60 tools, and a Chrome extension that carries your real LinkedIn session cookies — so your agents get JSON back instead of parsing HTML.

Why Voyager?

What You Can Do

• Profile intelligence (15 endpoints) — any profile, skills, contact info, email, recommendations, badges, relationship status, job-change insights
• Search (7 endpoints) + Lookups (7 endpoints) — people, companies, jobs, groups, content; lookups resolve names/locations/titles/industries to LinkedIn IDs for search filters
• Messaging (11 endpoints) — send, read, draft, mark-read, seen receipts, InMail, inbox export
• Connections & network (8 endpoints) — connect, accept, follow, unfollow, remove, invitations, network summary
• Content & engagement (13 endpoints) — feed, posts, comments, reactions, like, comment, create, articles, news
• Companies (12 endpoints) — company profile, employees, posts, followers, find-by-title, updates
• Sales Navigator (25 endpoints) — lead search with 28 structured filters, accounts, dossier, insights, relationship maps, similar companies, personas, alerts, inbox, credits
• Groups (9 endpoints) — membership, detail, members, posts
• Phantoms (46 endpoints) — batch/async workflows: auto-connect, auto-liker, company scraper, connections export, activity extractor, and more
• Webhooks — real-time events: message_received, message_seen, connection_received, session_expired, and more
• Batch operations — enrich up to 25 profiles, 20 relationships, or 10 companies in a single call
• MCP server — 60 tools over stdio for Claude Code, Claude Desktop, Cursor, or any MCP-compatible client

Architecture at a Glance

Your Agent ──▶ Voyager REST API ──▶ LinkedIn Voyager / SalesNav APIs
                      │
                      ├── Tier 1: Chrome extension relay (your real browser IP + cookies)
                      └── Tier 2: Direct HTTP + residential proxy (IPRoyal)

The core REST surface (Voyager, SalesNav, search, messaging, connections, engagement) is pure HTTP: a relay through the user’s Chrome extension when it’s connected, otherwise a direct call from the server using the synced cookies and a residential proxy. That’s why responses come back in 200ms–2s instead of the 15–30s a DOM-scraping approach takes.

As of 2026-04-22, every endpoint runs via REST/GraphQL. The handful of DOM-only phantoms that couldn’t be reversed against LinkedIn’s current surface (group invites, event invites, poll voters) were dropped rather than kept on life support.

Need Help?

• Email: support@scaleabm.org
• GitHub Issues: linkedin-voyager