Nexafon developer docs

Nexafon runs a business’s WhatsApp: the shared inbox, WhatsApp calls and team calls, and WhatsApp commerce (catalog, Shop menu, orders and payments). These docs show how to put all of it inside your product, so your users never leave it.

What you can build with

Piece	What it does	Start here
Web SDK	One script tag or npm package; Web Components for the whole dashboard (<nexafon-app>), the inbox, the softphone and a call button, themed with your colours	Quickstart
Server helpers	Sign user tokens and verify webhooks with one function call in Node, PHP, Python and Go	Server helpers
REST API (v1)	Conversations, messages, templates, teams, members, recordings, commerce and payments	API reference
Webhooks	Signed events for messages, calls, meetings, templates, billing and orders	Webhooks
Partner API	For platforms that run many stores: create stores, sign in their staff, receive every store’s events	Partners

How the pieces fit

1. Your server keeps a secret key and signs a short-lived user token for whoever is signed in to your product.
2. The page loads the SDK with your publishable key. The SDK swaps the user token for an SDK session that lives only in memory inside Nexafon’s frames.
3. Nexafon’s screens render inside your page; your code listens to events and calls methods such as call(phone).
4. Your server receives webhooks and calls the API with the secret key.

Core concepts explains workspaces, roles, keys, sessions and test mode in more detail.

For AI agents and tools

Every page is also served as Markdown: add .md to its path, such as /v1/quickstart.md. /llms.txt lists every page, /llms-full.txt has them all in one file, and the OpenAPI 3.1 spec is at /v1/api/openapi.json. The MCP server gives Claude Code and other MCP clients these docs, the example apps and test-key actions as tools.