Skip to content
14-day free trial, no card9 languages176 business types · 50 apps
EN· USD
Try a live demoStart free trial

Connect anything to zmle

A REST API with scoped keys and signed webhooks. Keep your own website, sync your other tools, or build on top of your workspace.

Create a lead from your own website

Authentication

Create a key in your workspace with only the scopes it needs. Send it as a bearer token. Keys can expire and be revoked at any time; only a hash of each key is stored.

# POST a lead from your own form 
curl -X POST https://yourname.zmle.com/api/v1/inquiries \
  -H "Authorization: Bearer $ZMLE_API_KEY" \
  -H "content-type: application/json" \
  -d '{"type":"QUOTE","name":"Dana Lee",
       "email":"dana@example.com",
       "subject":"AC service, 3 units"}'

# → 201 { "data": { "id": "…", "source": "api" } }

Documentation

Everything you need to build on a workspace: the REST API, webhooks, the MCP server for AI clients, API keys and a sandbox to try it.

  • API v1 reference

    Every endpoint of the REST API with its method, path and required scope, generated from the same OpenAPI document the API serves.

  • Webhooks

    Business events sent to your HTTPS endpoint as they happen: signed, retried on failure and logged.

  • MCP server

    Connect an AI client to a workspace through the Model Context Protocol, with the person's own permissions.

  • API keys and scopes

    What a key may read and write, and the limits it carries from the person who created it.

  • Sandbox workspace

    Try the API on a personal demo workspace with sample data. Nothing you do there reaches the outside world.

  • Security and data

    What the API, webhooks and the MCP server never send, how keys and signatures protect a workspace, and who is responsible once data reaches an AI client.

Webhooks

Subscribe an endpoint to the events you care about. Every delivery is signed with HMAC-SHA256 and a timestamp, retried with back-off if your server does not answer, and logged so you can replay it.

Limits and errors

Each key has a bucket of 300 requests, refilled at 5 per second, plus limits per address; clear JSON errors with codes, validation issues per field, and a version header on every response.

Some of the events

inquiry.createdquotation.acceptedinvoice.paidpayment.receivedorder.placedappointment.bookedpos.sale_completedstock.lowticket.createddeal.won

Want us to build the integration?

Our team connects zmle to your website, accounting tool or industry system as custom work.