App API

The same envelope, pagination, sorting, and filtering rules apply across every list and write endpoint.

{
  "success": true,
  "data": { /* endpoint-specific payload */ }
}

Create and manage scheduling invites — direct invites, multi-use mother invites, and the sub-invites issued from them.

• GET/api/v1/app/invites

  List invites visible to you. Returns root invites by default; filter, sort, and paginate with query parameters.

• POST/api/v1/app/invites

  Create a direct invite or a multi-use mother invite.

• GET/api/v1/app/invites/{inviteId}

  Fetch one invite's configuration and its booking, if any.

• PATCH/api/v1/app/invites/{inviteId}

  Update an active mother or direct invite. Sub-invites inherit from the mother and cannot be edited.

• GET/api/v1/app/invites/{inviteId}/sub-invites

  List the sub-invites issued from one mother invite.

• POST/api/v1/app/invites/{inviteId}/sub-invites

  Issue a candidate sub-invite from an active multi-use mother invite.

# Create a multi-use mother invite
curl -X POST https://<workspace>.kailenty.com/api/v1/app/invites \
  -H "X-API-Key: <api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "allowMultipleBookings": true,
    "publicLinkValue": "product/demo",
    "requiredAttendees": [{ "type": "users", "userIds": ["<user-id>"] }],
    "candidates": [],
    "voteDeadlineAt": "2026-07-01T00:00:00.000Z",
    "meeting": { "meetingDurationMinutes": 30, "title": "Product demo" }
  }'

List bookings, create meetings directly in Outlook and Teams, reschedule them, and check attendee availability.

• GET/api/v1/app/meetings

  List calendar bookings visible to you within a date range, with per-recruiter stats.

• POST/api/v1/app/meetings

  Create a meeting directly in Outlook and Teams without sending an invite. Up to 20 participants.

• PATCH/api/v1/app/meetings/{bookingId}

  Reschedule or edit a booked meeting. Changing the host is manager/admin only and recreates the event.

• PATCH/api/v1/app/meetings/{bookingId}/attendees

  Update a meeting’s optional attendees; required attendees stay unchanged.

• POST/api/v1/app/meetings/{bookingId}/availability

  Check whether the given users are free for a proposed time window.

List, create, and delete the attendee-group labels used to route invites and meetings.

• GET/api/v1/app/labelsManagers & admins

  List all labels in the workspace.

• POST/api/v1/app/labelsAdmins

  Create a label with a name, color, and description.

• DELETE/api/v1/app/labels/{id}Admins

  Delete a label. Returns 409 if it is still assigned to users or used in invites.

Read the workspace user directory and manage the labels assigned to each account.

• GET/api/v1/app/usersAdmins

  List users in the workspace with their assigned labels.

• PUT/api/v1/app/users/{id}/labelsAdmins

  Replace a user's labels with the supplied list of label IDs.

• 400Validation error — the request body or query failed a schema check.
• 401Unauthorized — the API key or bearer token is missing or invalid.
• 403Forbidden — your role is not allowed to perform this action.
• 404Not found — the invite, meeting, user, or label does not exist.
• 409Conflict — e.g. deleting a label that is still in use.

{
  "success": false,
  "error": "Validation failed",
  "message": "voteDeadlineAt must be in the future",
  "requestId": "req_..."
}