Everything Meetzy does, from your code.

Quick start

1. Create a key in Meetzy › Sales › Integrations & API › API keys. Copy it — it is shown once.
2. Call the API with the key as a Bearer token. GET /me tells you who the key belongs to.
3. Build: create a contact, open a deal, enroll them in a sequence, subscribe to deal.won.

curl https://meetzy.me/api/v1/me \
  -H "Authorization: Bearer $MEETZY_API_KEY"

const api = (path, body) => fetch(`https://meetzy.me/api/v1/${path}`, {
  method: body ? "POST" : "GET",
  headers: { Authorization: `Bearer ${process.env.MEETZY_API_KEY}`, "Content-Type": "application/json" },
  body: body && JSON.stringify(body),
}).then(r => r.json());

const contact = await api("contacts", { email: "camille@payfit.com", first_name: "Camille", company: "Payfit" });
const deal = await api("deals", { name: "Payfit — rollout", amount: 12000, primary_lead_id: contact.id });

Authentication

Every request carries an API key: Authorization: Bearer mz_live_…. A key belongs to the teammate who created it and acts as them — it sees their workspace and what it creates is signed with their name. Keys are revoked in the same screen; a revoked key answers 401 at once. The only calls that need no key are GET /catalog and the inbound workflow trigger, whose URL is its own secret.

New keys get read, write, webhooks and mcp; tick delete when you need it. Give each integration its own key, with only what it needs.

Requests and responses

• JSON in, JSON out: send Content-Type: application/json. Field names are snake_case.
• Ids are UUIDs. Dates are ISO 8601 (2026-10-07, 2026-10-07T09:30:00+02:00); times are returned in UTC.
• Amounts are numbers in the record’s currency (no cents conversion).
• PATCH changes only the fields you send. Fields Meetzy does not know are ignored.
• A POST that creates answers 201; other successes 200. Deletes answer { "deleted": true }.
• Creating something that exists by its natural key — a contact by email, a company by domain — returns the existing record instead of a duplicate.

Errors

Errors have a status code and a JSON body with a readable error, and sometimes details (for example { "code": "duplicate" }).

HTTP/1.1 409 Conflict
{ "error": "create property failed: this record already exists ((user_from, object_type, key)=(acme, contact, shoe_size))", "details": { "code": "duplicate" } }

Pagination, limits and retries

Webhooks and events

Instead of polling, subscribe to events: contact.created, contact.replied, deal.won, quote.accepted, task.overdue, contact.website_visit and 51 more. Deliveries are signed (HMAC-SHA256) and retried for about 8 hours. See Webhooks & events.

Tools

The reference