Exporting spreadsheets by hand
Every week somebody downloads the patient list to upload it into the CRM.
A public API to connect OCLÜ with n8n, Make, Zapier or your CRM
Add-on: contracted separately, on top of any plan
You connect OCLÜ with n8n, Make, Zapier or your CRM so appointments and patients travel between systems on their own, without exporting spreadsheets. It is a REST API in the OCLÜ dental software, switched on as an add-on over any plan.
What eats your time today in Public API
Systems that do not talk
The clinic's web form does not create the patient in the management system.
Impossible automations
With no API, any flow in n8n or Zapier ends in copying and pasting.
What Public API gives you in OCLÜ
REST API
You query clinicians, schedules, treatments with prices, operatories, free slots, appointments and patients; you create, move and cancel appointments and add patients.
n8n, Make and Zapier
It is used from n8n, Make or Zapier with their HTTP modules to automate the clinic's flows.
Read or write
Each key is created as read-only or read-and-write, and is shown only once when created.
Keys per location
Keys are created and revoked by the account owner or an administrator. Each one can be limited to certain locations and you see when it was last used.
Per location
Appointments, patients and operatories are requested by naming the location, so each integration works on the right clinic.
Usage limit
Up to 90 requests per minute per key. There are no webhooks: your system queries the API when it needs data.
How Public API works, in three steps
You switch on the add-on
You ask us to switch the public API on for the clinic's account.
You generate the key
The account owner creates the key, read-only or read-and-write, and copies it there and then.
You connect your tool
You configure n8n, Make, Zapier or your CRM using the reference documentation.
Frequently asked questions about the public API
Does OCLÜ have an API to integrate with other systems?
Yes. The OCLÜ public API is a REST API to connect the dental software with n8n, Make, Zapier or CRMs. It is switched on as an add-on over any plan.
What can you do with the API?
Query appointments, patients, clinicians, treatments and free slots; create, move and cancel appointments, and add patients. The medical history and payments do not come out through the API.
Who creates the keys and what permissions do they have?
The account owner or an administrator. Each key is read-only or read-and-write, can be limited to certain locations, is shown only once, and can be revoked whenever you want.
Does the API notify you when something happens in OCLÜ?
No. The API does not send webhooks: your system queries it when it needs data, with a limit of 90 requests per minute per key.
Do I need a developer?
To connect platforms such as n8n, Make or Zapier, a technically minded person following the documentation is enough. For bespoke integrations with your own CRM it is worth having a developer.
Public API connects to the rest of OCLÜ
Multi-location
Several clinics in one account, permissions per user
Security
Permissions per user, daily backups and an audit trail
Free from your own WhatsApp; automatic with the add-on
Try Public API with the rest of your clinic inside
The data your integration reads or writes is the same your team sees in OCLÜ, without exporting spreadsheets. Start free and migrate your data with our team.