If you want Check Cherry to talk to other software you use, the Check Cherry API is how you do it. It gives programmatic access to your events, leads, bookings, payments, and more, so you can connect Check Cherry to the rest of the tools you run your business on.
Who it's for
The API is a developer tool. Using it means writing and running code, not clicking through the app. That used to mean hiring a developer. It still can, but AI coding assistants like Claude Code, Cursor, and ChatGPT have lowered the bar a lot. If you are comfortable following technical steps, you can often get a working integration going yourself. Just know it is more hands-on than the no-code options below, which is all most businesses ever need.
Common reasons businesses build on the API:
- Sync events or bookings into another system you already use
- Pull leads or payment data into your own reporting or accounting setup
- Automate a workflow that would otherwise be manual data entry
- Connect Check Cherry to an internal tool you have built
For the complete list of what is available, including every endpoint, parameter, and example response, see the full reference at checkcherry.com/api/docs. That reference is the source of truth and stays current as the API grows.
Getting an integration key
Every request to the API is authenticated with an integration key. Each key is tied to the user who created it, which gives you a clean audit trail. A new key starts with no permissions. You choose them right after you create it, and a key can never have more access than the user it belongs to. You can create more than one key and revoke any of them individually, so it is common to use a separate key for each integration.
ik_) and store it somewhere safe.Building your integration
Share these basics with your developer. Everything else, including the endpoint list and response formats, is in the full reference.
- Base URL:
https://api.checkcherry.com/api/v1/ - Authentication: send the key as an
Api-Keyheader on every request. HTTPS only. - Format: requests and responses use JSON:API. List endpoints paginate with
pageandper.
A minimal authenticated request looks like this:
curl https://api.checkcherry.com/api/v1/events -H "Api-Key: ik_your_key_here"
The API is under active development. New fields and endpoints can be added at any time, so build defensively: have your integration ignore fields it does not recognize rather than break on them. We aim to give around 30 days of notice for changes that could break existing integrations, but designing for change is the safest approach.
Webhooks
Webhooks work in the other direction. Instead of your integration asking Check Cherry for changes, Check Cherry sends them to a URL you choose the moment a booking, lead, payment, or appointment is created or updated.
Add them on the same API Overview page: pick a trigger and enter the URL your developer gives you. Each webhook has a signing secret your developer can use to confirm a request really came from Check Cherry.
The webhooks guide lists every trigger with a sample payload and covers retries and signature checks.
What support can help with
The Check Cherry team is happy to help with the parts of the API that are ours to support:
In short, you own your integration. If you hit something that looks like a platform issue or an API bug, start the chat (the chat bubble in the lower right) and we will take a look.