> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clinikehr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Terms of Use

> The terms a workspace accepts to use the ClinikEHR API. Version 2026-10-03.

<p>
  {"Version 2026-10-03"}
</p>

<p>
  {"Effective: the date it is published on the API site."}
</p>

<p>
  {"These terms are between Bettar Platforms, Inc. (\"we\", \"us\"), a Delaware corporation with its registered office at 8 The Green, Suite B, Dover, DE 19901, United States, which operates ClinikEHR, and the organization that creates a developer workspace (\"you\"). By creating a workspace, or using a key issued to it, you agree to them. The person who accepts confirms they may bind the organization. An owner or administrator of the workspace also accepts them in the workspace's settings, and a live key cannot be created until they have. If your workspace already has live keys when a new version of these terms is published, those keys keep working for 30 days; after that they pause until an owner or administrator accepts the new version. Test keys are never paused."}
</p>

## 1. WHAT THESE TERMS COVER

<p>
  {"1.1 The API is the programming interface we provide to read and change records held in ClinikEHR."}
</p>

<p>
  {"1.2 A workspace is your organization's account for the API. A key is a credential issued to it."}
</p>

<p>
  {"1.3 A clinic is a clinic, pharmacy or laboratory that uses ClinikEHR. A connection is a clinic's recorded permission for your workspace to reach named kinds of its records."}
</p>

<p>
  {"1.4 These terms cover your use of the API. They do not give you any right to a clinic's records: only a clinic can give that, through a connection."}
</p>

<p>
  {"1.5 These terms are made up of this document, the Acceptable Use Policy, and, if you will receive patient information, the Data Protection Addendum for Organizations."}
</p>

## 2. A KEY ON ITS OWN REACHES NOTHING

<p>
  {"2.1 Records in ClinikEHR belong to the clinics that made them. A clinic decides whether to connect to you, which permissions to grant, and may narrow or withdraw them at any time without notice to you."}
</p>

<p>
  {"2.2 Every request is checked against the permissions on your key, the permissions the clinic granted, what the clinic's plan includes, and your plan. If any of them does not allow it, the request is refused."}
</p>

<p>
  {"2.3 You will not try to discover which clinics use ClinikEHR, or to reach a clinic that has not connected to you."}
</p>

## 3. TEST AND LIVE

<p>
  {"3.1 Test keys reach a sandbox of fictional data and are free. They never reach a real clinic."}
</p>

<p>
  {"3.2 Live keys require (a) verification of your organization, (b) a paid plan or a signed contract with us, and (c) acceptance of these terms by an owner or administrator of your workspace."}
</p>

<p>
  {"3.3 We may refuse or withdraw verification if the information you gave is inaccurate."}
</p>

## 4. YOUR KEYS AND YOUR PEOPLE

<p>
  {"4.1 You are responsible for every key issued to your workspace and everything done with it."}
</p>

<p>
  {"4.2 A key's secret is shown once. Store it as a secret. Never place it in software that runs on a device you do not control, in a web page, or in a public repository."}
</p>

<p>
  {"4.3 If a key may have been seen by someone who should not have it, revoke it at once and tell us."}
</p>

<p>
  {"4.4 You are responsible for the members of your workspace and what they do."}
</p>

## 5. WHAT YOU MAY NOT DO

<p>
  {"You will follow the Acceptable Use Policy, which is part of these terms."}
</p>

## 6. PATIENT INFORMATION

<p>
  {"6.1 You may receive patient information only if (a) your plan includes it, (b) we have approved your organization to receive it, and only the kinds of information we approved, as the Addendum sets out, (c) you have accepted the Data Protection Addendum for Organizations, and (d) a clinic has granted a permission that includes it."}
</p>

<p>
  {"6.2 Until all four are true, the API does not return patient information to you."}
</p>

<p>
  {"6.3 The Addendum is accepted only by an organization that will receive patient information. An organization that will not receive it does not need to accept it."}
</p>

## 7. CHANGES TO THE API

<p>
  {"7.1 The API is versioned. We may add routes, fields and permissions at any time; your software must ignore fields it does not know."}
</p>

<p>
  {"7.2 We will not remove a route or a field, or change its meaning, within a version without at least 6 months' notice, published in the API changelog and sent to your workspace's owners."}
</p>

<p>
  {"7.3 We may act sooner where a change is needed to protect the security of records or to comply with law. We will tell you as soon as we can."}
</p>

<p>
  {"7.4 We may withdraw the API as a whole on the same 6 months' notice, or sooner in the cases in 7.3."}
</p>

## 8. LIMITS, PLANS AND CHARGES

<p>
  {"8.1 Your plan states what is included and how use beyond it is charged. Prices are shown in your workspace, in United States dollars or in naira where you chose it."}
</p>

<p>
  {"8.2 Use beyond what is included is charged, not blocked, unless you have set a limit or a rate limit applies."}
</p>

<p>
  {"8.3 Fees are payable to Bettar Platforms, Inc. They are governed by the same terms as ClinikEHR's published Terms of Service, carried over here as follows."}
</p>

<p>
  {"8.4 Prices and taxes. All prices exclude applicable sales taxes, duties and levies. You are responsible for all fees incurred under your workspace. We may add new services for additional fees, or modify fees on thirty (30) days' prior written notice. Continued use after the effective date of a price change is acceptance of the new fees; if you do not agree to the revised fees, you may cancel before they take effect."}
</p>

<p>
  {"8.5 Billing. A paid plan is billed in advance on a recurring basis and renews automatically for a further period of the same length, at the then-current price for your plan, unless you cancel before the renewal date. Your renewal date and the amount payable are shown in your workspace's billing settings. You may cancel at any time; access to paid features continues until the end of the period already paid for."}
</p>

<p>
  {"8.6 No refunds. All fees paid are non-refundable. Once a payment has been processed it is fully earned on receipt, whether or not you keep using the API for the rest of the period. You are not entitled to a refund, credit or pro-rata reimbursement on cancellation, termination (voluntary or involuntary), downgrade or discontinuation of use, for any reason, including dissatisfaction, failure to use the API, a change in your business, or termination by us for breach. You had the opportunity to evaluate the API on the free sandbox plan before paying. This applies to the fullest extent the law that applies to you permits, and does not override rights that cannot be waived."}
</p>

<p>
  {"8.7 Downgrades. A downgrade takes effect at the start of the next billing cycle, with no refund or credit for the difference for the rest of the current period."}
</p>

<p>
  {"8.8 Failed payments. If a payment fails, we may retry the charge, suspend the workspace or terminate it. You remain liable for all unpaid fees, including any applicable late fees or collection costs."}
</p>

<p>
  {"8.9 Chargebacks and disputes. If you start a chargeback or payment dispute with your bank or payment provider, we may immediately suspend or terminate the workspace and pursue recovery of all amounts owed, including the disputed amount, administrative fees and any costs of the dispute. You agree to contact billing@clinikehr.com to resolve a billing concern before starting a chargeback."}
</p>

## 9. NOTIFICATIONS

<p>
  {"9.1 Where you register an address to receive notifications, you confirm you control it. We sign every notification; you must verify the signature before acting on it."}
</p>

<p>
  {"9.2 A notification says that something changed. It does not carry the record. You fetch the record, and your permission is checked when you do."}
</p>

## 10. AVAILABILITY AND SUPPORT

<p>
  {"10.1 We publish the status of the API. We make no commitment about its availability, and no plan includes one."}
</p>

## 11. SUSPENSION AND ENDING

<p>
  {"11.1 We may suspend a key or a workspace immediately if we reasonably believe it is compromised, is used in breach of these terms, or threatens the security of any clinic's records. We will tell you as soon as practicable and in any case within 24 hours."}
</p>

<p>
  {"11.2 You may close your workspace at any time. We may end these terms on 30 days' notice."}
</p>

<p>
  {"11.3 When a workspace closes, its keys stop working and its connections end. What you already received from a clinic remains subject to your agreement with that clinic and to the Addendum."}
</p>

<p>
  {"11.4 Sections 12, 13, 15, 16 and 17, and anything else that by its nature is meant to continue, continue after these terms end."}
</p>

## 12. CONFIDENTIALITY

<p>
  {"12.1 Each party will keep the other's confidential information confidential, use it only to perform or use the API under these terms, and disclose it only to people who need it for that and are bound to keep it confidential."}
</p>

<p>
  {"12.2 Confidential information means what one party gives the other in confidence or that a reasonable person would understand to be confidential, including your keys, our security information, and the names of the providers we use that we give you on request. It does not include information that is public through no fault of the receiving party, that the receiving party already had or learned independently, or that it received lawfully from someone else."}
</p>

<p>
  {"12.3 A party may disclose confidential information where the law or a court requires it, after telling the other party first where it may lawfully do so."}
</p>

<p>
  {"12.4 Patient information is not covered by this section. It is governed by the Addendum, the clinic's agreement with you, and the law."}
</p>

## 13. INTELLECTUAL PROPERTY

<p>
  {"13.1 We and our licensors own the API, its documentation, the software development kits we publish, and ClinikEHR. These terms give you a limited, non-exclusive, non-transferable right to use them to connect your software to ClinikEHR while these terms are in force."}
</p>

<p>
  {"13.2 You own your software and your data. Records held by a clinic belong to that clinic."}
</p>

<p>
  {"13.3 You will not copy, modify or resell the API or its documentation except as we allow, or try to obtain our source code."}
</p>

<p>
  {"13.4 If you give us feedback about the API, we may use it without owing you anything."}
</p>

<p>
  {"13.5 These terms give you no right to use the name or logo of Bettar Platforms, Inc. or ClinikEHR except to say truthfully that your software connects to ClinikEHR."}
</p>

## 14. WARRANTIES

<p>
  {"14.1 Each party confirms that it has the power to enter into these terms."}
</p>

<p>
  {"14.2 You confirm that the information you gave us about your organization is accurate, and that you will use the API lawfully."}
</p>

<p>
  {"14.3 We provide the API as it is and as it is available. To the fullest extent the law allows, we give no other warranty, including of merchantability, of fitness for a particular purpose, or that the API will be uninterrupted or error-free."}
</p>

<p>
  {"14.4 The API is not medical advice and is not a substitute for the judgment of a clinician."}
</p>

## 15. LIABILITY

<p>
  {"15.1 Our total liability to you arising out of or relating to these terms, whether in contract, tort or otherwise, is limited to the fees you paid us for the API in the 12 months before the claim arose."}
</p>

<p>
  {"15.2 To the fullest extent the law allows, neither party is liable to the other for lost profits, lost revenue, loss of data, or indirect, special, incidental or consequential damages."}
</p>

<p>
  {"15.3 Nothing in these terms limits liability that cannot be limited by law."}
</p>

<p>
  {"15.4 Liability for patient information is dealt with in the Addendum."}
</p>

## 16. INDEMNITY

<p>
  {"16.1 You will defend and compensate us against a claim by a third party, including a clinic or a patient, to the extent it arises from your use of the API in breach of these terms or the Acceptable Use Policy, or from your use of information you received through the API."}
</p>

<p>
  {"16.2 We will tell you promptly of the claim, let you control its defence, and give reasonable help at your cost. You will not settle it in a way that admits fault on our part without our written consent."}
</p>

## 17. GOVERNING LAW

<p>
  {"17.1 These terms, and any dispute arising out of them, are governed by the laws of the State of Delaware, United States, without regard to its conflict-of-law rules."}
</p>

<p>
  {"17.2 Disputes are subject to the dispute resolution terms of the ClinikEHR Terms of Service."}
</p>

<p>
  {"17.3 If you are established in Nigeria, the Addendum adds terms for the Nigeria Data Protection Act."}
</p>

## 18. GENERAL

<p>
  {"18.1 These terms are the whole agreement between us about the API. Where they conflict with the Acceptable Use Policy or the Addendum about patient information, the Addendum applies."}
</p>

<p>
  {"18.2 If we change these terms in a material way, we will publish the new version and ask an owner or administrator of your workspace to accept it; a correction of wording does not need acceptance."}
</p>

<p>
  {"18.3 Notices to us go to support@clinikehr.com. Notices to you go to your workspace's owners."}
</p>

<p>
  {"18.4 You may not transfer these terms without our written consent."}
</p>

## PROVIDERS

<p>
  {"We use providers of hosting, payment, email and similar services to run ClinikEHR. They are described by category, not by name. We give their names on request, in confidence."}
</p>

<p>
  {"ClinikEHR is a product of Bettar Platforms, Inc."}
</p>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.