MetoCRM
API & Webhooks
MetoCRM is open in both directions: leads come in from any external form over the API, and the CRM sends webhooks out to your own systems when something happens. Nothing is copied by hand in between.
The inbound lead API
A form on your own website, a landing page, a call-centre tool, a script you wrote — anything that produces leads can post them to a single endpoint. The moment a record arrives it enters the CRM's normal flow: lead distribution runs, the record lands with a consultant, and any automations you defined fire.
The fields you send:
- Name — required.
- Email or phone — at least one is required. You can send both.
- Notes — free text from the form; a single string or a list of fields.
- Language code — the patient's language, matched against the languages defined in the CRM.
- Advertising channel code and ad code — which channel and which ad the record came from.
- Patient status code — the status the record opens in.
- Sales group — the sales team the record belongs to.
Channel, status and language are sent as codes, and the valid codes are read from the API's own reference endpoints (advertising channels, patient statuses, sales groups, languages). Whoever writes the integration never has to log in and hunt for an ID.
The Zapier branch
For teams connecting without code there is a separate Zapier branch: its own key, its own lead-import endpoint and the same reference lists. Records from the thousands of tools Zapier connects to — Typeform, Google Sheets, Calendly, your own CMS — land in MetoCRM through it.
Records arriving via Zapier are marked with their source inside the CRM, so "came in over the API" and "came in through Zapier" stay separable in reporting. That distinction matters when you measure channel performance.
Outbound webhooks
The other direction is open too. When you build an automation you can pick webhook as the action: when the trigger fires, MetoCRM sends a GET or POST request to the address you provide.
In practice: telling your accounting software when a patient's status becomes "sale closed", updating your own dashboard when a particular tag is applied, or notifying a partner system when an operational step completes. It is configured in the same flow as the other automation actions — send a message, change a status, set a reminder, place a call.
Keys and access
Every integration runs on its own key, and a key belongs to a single account. Key management lives inside the CRM: issue, list, revoke. A request made with a revoked key is refused immediately — which is the entire task when you part ways with the agency that built the integration.
There is a separate verification endpoint for testing a key, so whoever builds the integration can check the connection before sending a single lead.
The connections people build most
- Website forms — Your own form writes straight into the CRM; no submission sits forgotten in an inbox.
- Landing pages — Every campaign landing page can send its channel and ad code, so the record lands in the right breakdown.
- Call centres and outsourced teams — Records collected by an external team flow in over the API instead of waiting for manual entry.
- Accounting and reporting — An outbound webhook triggers your finance system the moment a sale closes.
- Ad measurement — Records arriving with a channel and ad code are the precondition for ever measuring which ad produced a patient.
Frequently asked questions
Does MetoCRM have an API?
Which fields does the lead API need?
Do leads from the API trigger automations?
What is the difference between Zapier and the API?
Which events can send a webhook?
Related pages
Let's build the integration together
In the demo we map which fields come from which source, against your own flow.