Skip to content
Quenza
MCPNew: use this help center in Claude, ChatGPT or CursorConnect →

Quenza API

Connect Quenza to your own systems with the REST API, and create and update clients, groups, team members and tasks with simple JSON requests.

The Quenza API lets your own software work with your Quenza workspace. Your website, CRM or booking system can add clients, put them in groups, invite team members and read tasks, without anyone typing details into Quenza by hand.

For example, Bright Path Coaching sells an eight-week mindfulness course on its website. When someone buys it, the website creates the client in Quenza and adds them to the Mindfulness group. The client gets their invitation right away, and Sarah Bennett sees them in her client list the next time she opens Quenza.

This part of the help center is for developers. If you only need to create a token for your developer, see API token. For inspiration, start with What you can build. If you would rather not write code, tools like Zapier or Make can call the API for you.

You need an API token. A workspace Owner or Manager creates it under Developer Tools → API Token; see Authentication. Store it in an environment variable, so it never ends up in your code:

Terminal window
export QUENZA_API_TOKEN="your token"

Then ask for the first client in your workspace:

Terminal window
curl "https://developers.quenza.com/v1/clients?limit=1" \
-H "Authorization: Bearer $QUENZA_API_TOKEN" \
-H "Accept: application/json"

Quenza answers with JSON. A list always has the records in data, and meta and links for pagination:

{
"data": [
{
"id": "8GJ4D9KQ",
"email": "emma.clarke@example.com",
"first_name": "Emma",
"last_name": "Clarke",
"status": "active"
}
],
"meta": { "limit": 1, "offset": 0, "total": 24 },
"links": { "next": "https://developers.quenza.com/v1/clients?limit=1&offset=1", "prev": null }
}

The example is shortened: a client has more fields, listed in List clients.

The API does not cover activities, programs, activity results, notes or chats. To hear from Quenza when something happens, such as a new client or an accepted invitation, use webhooks.

  • Base URL: every endpoint starts with https://developers.quenza.com/v1. The API only answers over HTTPS.
  • JSON in, JSON out: send Accept: application/json with every request, and Content-Type: application/json with every POST and PATCH, also when there is no body. See Errors for what happens without them.
  • One workspace per token: a token belongs to one workspace and acts as the professional who created it. Clients and groups you create are assigned to that professional.
  • IDs are text: IDs such as 8GJ4D9KQ are short strings. Store them as they are; do not turn them into numbers.
  • Times in UTC: times are ISO 8601 in UTC, such as 2026-11-15T10:00:00.000000Z. Dates without a time, such as a birthdate, are YYYY-MM-DD.
  • Every field, every time: responses always contain every field. A field without a value is null.

Download the Postman collection to send every request of this reference from Postman, Insomnia or Bruno with your own token. Tools and code generators read the OpenAPI file.

Enlarged screenshot from this article