userId

attendeeEmail

Recurring event ID if the event is recurring

Acceptable values one of ["ACCEPTED" "PENDING" "CANCELLED" "REJECTED"]

"ACCEPTED" "PENDING" "CANCELLED" "REJECTED"

Cancel all remaining bookings (in case of recurring)

ID of the event type to which the custom input is being added

If the custom input is required before booking

The ID of the eventType it is associated with

Number of minutes of buffer time after a Cal Event

Number of minutes of buffer time before a Cal Event

If the event type should disable adding guests to the booking

Minimum time in minutes before the event is bookable

A list of all locations for the event type

If calendar days should be counted for period days

The position of the event type on the public booking page

The intervals of available bookable slots in minutes

A valid URL where the booker will redirect to once the booking is completed successfully

teamId

integration of the selected calendar to get

integration

externalId of the selected calendar to get

externalId

userID

A unique slug that works as path for the team public page

Email that belongs to the user being edited

Emailthat belongs to the user being edited

subscriberUrl

The events which should trigger this webhook call

eventTriggers

Whether the webhook is active and should trigger on associated trigger events

active

payloadTemplate

The event type ID if this webhook should be associated with only that event type

eventTypeId

A template to customize the webhook payload

Cal API

Pre-configured, Predictable, Single Interface, Ready-to-use, Opinionated & Managed API Explorer & Server - LowCodeAPI

Pre-configured, Predictable, Single Interface, Ready-to-use, Opinionated & Managed API Explorer & Server. Bring your API credentials, configure and access your 3rd party APIs. Using LowCodeAPI securely manage all integrations in one place.

LowCodeAPI

Featured

OpenAI

Google Sheets

Google Docs

Notion

Gmail

gmail

Unsplash

UnsplashAPI

Trello

Trello API

Telegram

Telegram API

The Stripe API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.