EzBizi Developers API reference →

EzBizi for developers

Connect your own script, or an AI like Claude, to EzBizi: read and update leads, customers, jobs and the rest of your company's records through the same API the app uses.

API base: https://app.ezbizi.com/api/v1. Every answer is JSON. The API reference lists every endpoint a key can call. It is generated from the app's own route table, the same list the MCP tool list_endpoints returns, so an endpoint appears there the day it ships.

Get started

  1. Sign in to EzBizi, open your account (your name or picture) and go to API keys.
  2. Press New API key, say what it is for (for example "Claude on my laptop") and choose its level: Viewer, Editor or Full access. Your role decides which levels you may make.
  3. Copy the key. It is shown once and only its hash is kept, so put it in a password manager or secret store, never in code or a web page.
  4. Send it on every request: Authorization: Bearer <key>.
curl https://app.ezbizi.com/api/v1/me \
  -H "Authorization: Bearer $EZBIZI_API_KEY" \
  -H "Accept: application/json"

Keys and permissions

A key acts as the person who made it. It can do, through the API, what that person can do in the app with their role, and nothing more: the same permissions, the same companies and branches, the same checks on every record. Treat it like a password and revoke it from API keys as soon as you think it has leaked.

Levels

LevelMethodsYour role needs
ViewerGET onlyAPI keys › View
Editoralso POST, PUT, PATCH; no DELETEAPI keys › Edit
Full accessevery methodAPI keys › Delete

The role is checked again on every request, so narrowing a role downgrades or stops the keys its people already made. In the reference, x-key-level on each operation is the lowest level its method needs; the role's own permissions still apply on top.

Choosing a company or branch

Like the app, a request can say which part of the organization it is looking at with X-EzBizi-View: organization, company:<id> or franchise:<id>. Leave it out to use the person's default view.

What a key can never do

No key, whatever its level, can change the password, two-step sign-in, sign-in text codes or signed-in sessions, make or revoke API keys, or delete the account. Those answer 403 api_key_account_security; do them in the app.

How long a key lasts

A key does not expire on its own and never signs out for being idle. It lasts until it is revoked, or until the person's password is reset, which removes all of their keys. To rotate without a gap, make the new key, deploy it, then revoke the old one.

Limits

The MCP endpoint takes 120 requests a minute. Some other endpoints carry their own limits. Over a limit the API answers 429 with a Retry-After header in seconds; wait that long before trying again.

Lists take their own paging parameters, listed per endpoint in the reference. Through MCP, an answer too large to send whole comes back in pages (offset, limit, next_offset) or as an outline of its keys, never cut off mid-way.

Errors

An error is JSON with a sentence for people and, where the app has one, a stable code for programs:

{ "message": "This API key can only read. A Viewer key cannot make changes.", "code": "api_key_read_only" }

Decide what to do from the HTTP status and code; message is written for people and can change. Validation errors (422) also carry errors, by field.

HTTPcodeMeaning
401The key is missing, wrong or revoked.
402subscription_inactiveThe organization's subscription has ended. It is read-only.
403api_key_read_onlyA Viewer key tried to change something.
403api_key_no_deleteAn Editor key tried to delete. Deleting needs Full access.
403api_key_not_allowedThe person's role no longer allows API keys.
403api_key_account_securitySign-in security and account deletion are done in the app only.
403permission_deniedThe person's role does not allow this.
404No such record, or not one this person can reach.
422The request was not valid; see errors.
429Too many requests. Wait for Retry-After.

Quickstarts

Each example reads the newest leads as the key's owner.

curl

curl "https://app.ezbizi.com/api/v1/leads" \
  -H "Authorization: Bearer $EZBIZI_API_KEY" \
  -H "Accept: application/json"

JavaScript (fetch)

const res = await fetch("https://app.ezbizi.com/api/v1/leads", {
  headers: { Authorization: `Bearer ${process.env.EZBIZI_API_KEY}`, Accept: "application/json" },
});
if (!res.ok) throw new Error(`${res.status} ${(await res.json()).message}`);
console.log(await res.json());

Python (requests)

import os, requests

r = requests.get(
    "https://app.ezbizi.com/api/v1/leads",
    headers={"Authorization": f"Bearer {os.environ['EZBIZI_API_KEY']}", "Accept": "application/json"},
)
r.raise_for_status()
print(r.json())

PHP

$ch = curl_init('https://app.ezbizi.com/api/v1/leads');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => ['Authorization: Bearer '.getenv('EZBIZI_API_KEY'), 'Accept: application/json'],
]);
$leads = json_decode(curl_exec($ch), true);

Run these from a server or your own computer. Never put a key in a web page or a mobile app, where anybody can read it.

MCP

EzBizi is an MCP server, so an AI such as Claude can work in EzBizi as you. Endpoint: https://app.ezbizi.com/api/v1/mcp (Streamable HTTP, JSON answers), authenticated with the same API key.

Tools

Two tools reach the whole API rather than a hand-picked slice of it, so the AI never gets more than the key's owner has, and a new endpoint is reachable the day it ships.

Claude Code

claude mcp add --transport http ezbizi https://app.ezbizi.com/api/v1/mcp \
  --header "Authorization: Bearer $EZBIZI_API_KEY"

Then ask, for example, "list my open leads from this week". The API keys screen also shows this line, with your new key in it, when you make one.

Other MCP clients

Any client that can send an Authorization header to an HTTP MCP server works, for example Claude Desktop through a local bridge, Cursor or VS Code:

{
  "mcpServers": {
    "ezbizi": {
      "type": "http",
      "url": "https://app.ezbizi.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

Not yet: sign-in with OAuth, which connectors added from claude.ai or ChatGPT require, and SSE streaming.

Activity log

Every call a key makes is recorded, refused ones too: method, path, status, whether it came through MCP, the key's level and the address it came from. A change also keeps what was sent and, for an update or delete, the record as it was just before. Open API keys › Activity to read your own keys' calls; an Administrator sees the whole organization's. Some changes, such as edits to a customer or to website text, can be put back from there with one press.

Webhooks

To have EzBizi call your system when something happens, use an automation: Automations › any trigger › Call a webhook. When the webhook has a signing secret, each request carries X-EzBizi-Timestamp and X-EzBizi-Signature, the hex HMAC-SHA256 of timestamp.body with that secret. Check it before trusting the body:

import hmac, hashlib

def is_from_ezbizi(secret: str, timestamp: str, body: bytes, signature: str) -> bool:
    expected = hmac.new(secret.encode(), timestamp.encode() + b"." + body, hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected, signature)

A request that fails with a server error or times out is tried again.

EZBIZI LLC · Last updated 6 November 2026 · Home · Privacy · Terms · Support