# client.created

> The client.created webhook tells your server about every new client or guest in Quenza, with their name, email address, status and who added them.

Available on the Growth plan and higher.

Source: https://quenza.com/help/api/webhooks/client-created/

Quenza sends `client.created` as soon as a client or guest is added to your workspace. Use it to add new clients to your CRM or mailing list, or to tell your team that someone new has joined.

It is sent for every way a client is added:

- by hand, also as a guest without an account ([Add clients](https://quenza.com/help/clients/add-clients/)),
- by [import](https://quenza.com/help/clients/import-clients/), once per imported client,
- through the API, with [Create a client](https://quenza.com/help/api/clients/create-a-client/),
- through a [landing page](https://quenza.com/help/new-clients/landing-pages/) signup,
- when a guest is converted to a client with an account. The `id` stays the same, so your server receives the same client a second time, now with `is_guest` set to `false`.

It is not sent when a client's details change or when a client is archived. The invitation email goes out at the same time; when the client sets up their account, [`client.invitation_accepted`](https://quenza.com/help/api/webhooks/client-invitation-accepted/) follows.

## Request

`POST` to your webhook address, with the header `X-Quenza-Event: client.created`. See [Receive webhooks](https://quenza.com/help/api/webhooks/) for all headers, retries and how to check the request.

```json
{
  "client": {
    "id": "8GJ4D9KQ",
    "email": "emma.clarke@example.com",
    "first_name": "Emma",
    "last_name": "Clarke",
    "is_guest": false,
    "status": "pending",
    "created_at": "2026-11-15T09:30:00+00:00"
  },
  "invited_by": {
    "id": "H2V7N4QX",
    "email": "sarah.bennett@example.com",
    "first_name": "Sarah",
    "last_name": "Bennett"
  }
}
```

## Fields

### client

| Field | Type | Description |
| --- | --- | --- |
| `id` | string | The client's ID, the same as in the API. Use it to [get the client](https://quenza.com/help/api/clients/get-a-client/) and to recognise a client you have already processed. |
| `email` | string | The client's email address. |
| `first_name` | string | The client's first name. |
| `last_name` | string | The client's last name. |
| `is_guest` | boolean | `true` for a guest without an account or login, `false` for a client. |
| `status` | string | `pending` while the client has not accepted their invitation, `active` for an active client or a guest, `archived` for an archived client. |
| `created_at` | string | When the client was added, ISO 8601 with offset, such as `2026-11-15T09:30:00+00:00`. |

### invited_by

The professional who added the client. For a landing page signup, it is the professional the signup form assigns new clients to; for an API request, the professional who created the token.

| Field | Type | Description |
| --- | --- | --- |
| `id` | string | The professional's ID, the same as in [List members](https://quenza.com/help/api/members/list-members/). |
| `email` | string | The professional's email address. |
| `first_name` | string | The professional's first name. |
| `last_name` | string | The professional's last name. |
