Skip to main content
The ClinikEHR API lets another system — your own website, a partner’s software, an internal report — read straight out of your ClinikEHR workspace, without anyone exporting a file by hand. You create the key yourself, from inside your own workspace, and choose exactly what it can see.

​
What it opens today

By default, a key you create reads your workspace’s own inventory: locations, catalogue items, availability, and exact stock levels. The API add-on is what opens everything else your own keys can reach — patients, appointments, clinical notes, and your CRM — still only with keys you create yourself, for your own systems. See API access for the full walkthrough, including the add-on and the API data agreement your patient records need before they’re reachable. You can also let another organization — a marketplace, a billing partner — connect to your workspace directly, item by item, under Connected organizations on the same tab. Nothing is ever shared without you approving it.

​
Where the documentation is

Full endpoint reference, authentication, error codes, permissions and guides are at docs.clinikehr.com. If you’re the one writing the integration (rather than the one creating the key), that’s where to send your developer.

API access

Create a key, connect another organization, and buy the add-on that opens your patient records.

Export your data

Getting your own records out as CSV or ZIP, no code required — for a one-off, not an integration.

HIPAA and compliance

What governs clinical data however it is accessed.

Contact support

Questions about a key, a connection, or the add-on.

​
Not to be confused with ClinikAPI

ClinikAPI is a separate product — a FHIR R4 developer platform for building your own healthcare software from scratch, licensed on its own, apart from any ClinikEHR subscription. It does not read a ClinikEHR clinic’s records; if you’re trying to get data out of your own ClinikEHR workspace, the API access above is what you want, not ClinikAPI. If you’re building an independent product and want FHIR, SDKs and embeddable components, see docs.clinikapi.com.