Skip to main content
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

Exchange credentials for a JWT, then send it as a Bearer token on every request. 
curl -X POST "https://api.izap.ai/api/v1/auth/jwt/login" \
     -H "Content-Type: application/x-www-form-urlencoded" \
     -d "username=$IZAP_EMAIL&password=$IZAP_PASSWORD"
# -> {"access_token":"<JWT>","token_type":"bearer"}

curl "https://api.izap.ai/api/v1/businesses" \
     -H "Authorization: Bearer $IZAP_TOKEN"
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, scheduling, 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

One OAuth 2.0 server for both the API and the MCP. Bearer JWTs for server-to-server, authorization-code + PKCE for interactive apps.

​
Drive iZap from an agent

Register the Analytics MCP as a remote HTTP server and your agent can call iZap’s tools with the same token as the REST API. 
{
  "mcpServers": {
    "izap": {
      "type": "http",
      "url": "https://api.izap.ai/mcp",
      "headers": { "Authorization": "Bearer ${IZAP_TOKEN}" }
    }
  }
}

See the full MCP tool catalog

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

​
Environments

EnvironmentAPI originMCP URL
Productionhttps://api.izap.aihttps://api.izap.ai/mcp
Staginghttps://api-staging.izap.aihttps://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.