Navigent REST API: full developer access, Q3 2026.
Navigent REST API for running the campaigns you already build inside Navigent: OAuth 2.0, scoped tokens, JSON over HTTPS, full coverage of your own sequences, campaigns, webhooks, and the unified inbox. Sandbox now.
REST
JSON over HTTPS
OAuth 2.0
Scoped auth
Q3 2026
Public launch
Early access
Sandbox now
What you'll be able to do.
Every workflow you build inside Navigent will be addressable from your stack, so you can wire your own campaigns into the tools your team already runs. The API is scoped to data inside your workspace. It is not a contact database product and does not let you query, export, or resell the wider B2B contact database.
Create, pause, and edit multi-step sequences across email, LinkedIn, WhatsApp, Instagram, and SMS via REST without touching the UI, with full conditional branching support.
Manage prospect lists you have already imported or built inside the app: update contacts, attach custom fields, push them through sequences, and sync custom fields back to your CRM. The API operates only on contacts already saved to your workspace.
Spin up campaigns, clone winners, A/B test variants, and pull per-step open, reply, click, and meeting metrics into your dashboards with millisecond latency.
Subscribe to webhooks for reply, bounce, meeting booked, opt-out, sequence-complete, and lead-score-change events with at-least-once delivery and HMAC signing.
Read and write lead scores (0 to 100) on your own contacts, fire score-change events into downstream tools, and trigger plays the moment a prospect crosses your threshold.
Sync the unified inbox two-way: pull threads into your helpdesk, post replies back, and keep status (assigned, snoozed, resolved) in lockstep across systems.
Authenticate with OAuth 2.0 and scoped tokens (read:contacts, write:sequences, admin:workspace) so you grant exactly the permissions your integration needs.
Respect documented rate limits per endpoint with burst and sustained tiers, 429 retry-after headers, and a usage dashboard inside the developer settings page.
Idempotent every POST via Idempotency-Key headers so retries from your worker queue never create duplicate contacts, campaigns, or webhook subscriptions.
Build with Node, Python, and Go SDKs ready at public launch in Q3 2026, plus a typed OpenAPI 3.1 spec for code generation in any language.
Test in the sandbox today with isolated data, simulated reply and bounce events, and free tier credits before paying for production capacity.
Audit every request, response code, and payload size per API key with optional export to your SIEM via webhook.
Frequently asked questions
How do I authenticate with the Navigent REST API?
+
Navigent uses bearer token authentication. Generate an API key from your workspace settings, then pass it in the Authorization header as 'Bearer YOUR_API_KEY' with every request.
What are the Navigent API rate limits?
+
Solo plans get 60 requests per minute, Pro plans get 300 requests per minute, and Agency plans get 1,000 requests per minute. Rate limit headers are returned with every response so you can throttle clients accordingly.
Does Navigent offer official SDKs?
+
Yes, official SDKs are available for Node.js, Python, Go, and PHP. All SDKs are open source on GitHub and ship with TypeScript definitions where applicable.
How do Navigent webhooks work?
+
Configure webhook endpoints in your workspace to receive real-time events for new replies, campaign status changes, and contact updates. Payloads are signed with HMAC SHA-256 so you can verify authenticity.
Which endpoints are available in the Navigent API?
+
Core endpoints cover campaigns, sequences, unified inbox messages, lead scores, team members, and the contacts you have already saved into your workspace. Every resource is scoped to your workspace. The API does not expose a search or export endpoint over the wider B2B contact database.
Can I use the API to pull leads from the wider contact database?
+
No. The B2B contact database is licensed for in-product use only. You can search and reveal prospects through the in-app finder to run your own campaigns, but the API does not expose a search or export endpoint over the wider database. The API only operates on contacts already saved inside your workspace.
Is the Navigent API versioned?
+
All endpoints are versioned via the URL path, currently 'v1'. We provide a minimum of 12 months notice and parallel availability before deprecating any version.
Where can I find Navigent API documentation?
+
Full reference docs, request examples, and interactive playgrounds are available at developers.navigent.io. Each endpoint includes sample code in cURL, Node.js, Python, Go, and PHP.
Keep exploring
Get a sandbox key before everyone else.
Join the early access list and we'll ship you credentials, docs, and a direct line to the API team the week your sandbox opens.