Build on iZap

iZap runs WhatsApp-first business automation: AI assistants handle customer conversations, orders, and scheduling. This is where you build on top of it — call the REST API or drive it from an AI agent over the MCP server. Same business logic, same OAuth 2.0 auth, everywhere.

Get an access token and make your first call

Zero to an authenticated request in a few minutes.

Open the dashboard

Manage assistants, businesses, and API access.

Your first call

Create a personal access token in the dashboard under User Settings → API Keys, then send it as a Bearer token on every request.

curl "https://api.izap.ai/api/v1/businesses" \
     -H "Authorization: Bearer $IZAP_TOKEN"

import os, httpx

r = httpx.get(
    "https://api.izap.ai/api/v1/businesses",
    headers={"Authorization": f"Bearer {os.environ['IZAP_TOKEN']}"},
)
print(r.json())

const res = await fetch("https://api.izap.ai/api/v1/businesses", {
  headers: { Authorization: `Bearer ${process.env.IZAP_TOKEN}` },
});
console.log(await res.json());

Personal access tokens are available on plans that include the REST API. If API Keys is missing from your settings, your plan does not include it.

For third-party apps, use the OAuth 2.0 authorization-code + PKCE flow instead of storing credentials — see Authentication.

Skip the boilerplate: npx @izap/wizard scaffolds a working REST, MCP, webhook, or SSE client into your stack. See the setup wizard.

What you can build

REST API

Chats, businesses, templates, and broadcasts under /api/v1. JSON in, JSON out, versioned and predictable.

Analytics MCP

Point Claude, ChatGPT, or your own agent at {origin}/mcp and call analytics and assistant-management tools directly.

Authentication

Personal access tokens for server-to-server, and one OAuth 2.0 server (authorization-code + PKCE) for interactive apps and the MCP.

Drive iZap from an agent

Register the Analytics MCP as a remote HTTP server and your agent can call iZap’s tools. The client signs in over OAuth the first time it connects.

{
  "mcpServers": {
    "izap": {
      "type": "http",
      "url": "https://api.izap.ai/mcp"
    }
  }
}

Agents that can’t complete an interactive sign-in send a Bearer token instead; see Analytics MCP for server-to-server setup.

See the full MCP tool catalog

Assistant management, message stats, conversation analytics, and keyword search.

Environments

Environment	API origin	MCP URL
Production	`https://api.izap.ai`	`https://api.izap.ai/mcp`
Staging	`https://api-staging.izap.ai`	`https://api-staging.izap.ai/mcp`

The REST API is versioned under /api/v1; breaking changes move to a new version path. The interactive Endpoints reference in the API reference tab is generated from the curated OpenAPI spec and is authoritative for request and response shapes.

Keep going

Quickstart

The full walkthrough, token to first call.

API status

Live health of the production API.

AI Trainer

Train and refine your WhatsApp assistants.

Get started

Guides

Get an access token and make your first call

Open the dashboard

Your first call

What you can build

REST API

Analytics MCP

Authentication

Drive iZap from an agent

See the full MCP tool catalog

Environments

Keep going

Quickstart

API status

AI Trainer

Get an access token and make your first call

Open the dashboard

​Your first call

​What you can build

REST API

Analytics MCP

Authentication

​Drive iZap from an agent

See the full MCP tool catalog

​Environments

​Keep going

Quickstart

API status

AI Trainer

Your first call

What you can build

Drive iZap from an agent

Environments

Keep going