---
title: "Cal.com"
description: "Read an authorized Cal.com profile and a bounded dated bookings page. Personal OAuth is isolated per account. Reads do not cover all busy times or follow pages. Regular unpaid booking writes require separate read-write a"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Cal.com

<p>Read an authorized Cal.com profile and a bounded dated bookings page. Personal OAuth is isolated per account. Reads do not cover all busy times or follow pages. Regular unpaid booking writes require separate read-write authorization and an exact interactive human approval.</p>

<details data-command-index><summary>What you can do (9)</summary>
<h2>What you can do</h2>
<p>Available commands: 9 (6 read, 3 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/calcom#command-calcom-users-me">Read connected profile</a> — <code>calcom.users.me</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calcom#command-calcom-bookings-list">List dated bookings</a> — <code>calcom.bookings.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calcom#command-calcom-event-types-list">List own event types</a> — <code>calcom.event-types.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calcom#command-calcom-event-types-get">Read own event type</a> — <code>calcom.event-types.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calcom#command-calcom-bookings-get">Read booking</a> — <code>calcom.bookings.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calcom#command-calcom-slots-list">List dated available slots</a> — <code>calcom.slots.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calcom#command-calcom-bookings-create">Create a regular unpaid booking</a> — <code>calcom.bookings.create</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calcom#command-calcom-bookings-reschedule">Reschedule one unpaid booking</a> — <code>calcom.bookings.reschedule</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calcom#command-calcom-bookings-cancel">Cancel one unpaid booking</a> — <code>calcom.bookings.cancel</code></td>
<td>Write</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/calcom">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Cal.com, then enter the issued values in the connection form below.</p>
<ol>
<li>Create a Cal.com API key under Settings → Developer → API keys and enter it as Access token. For OAuth, register a client with the exact redirect URI, enter Client ID/Secret, save and authorize. Enable read-write only for booking changes and check account permissions.</li>
</ol>
<p><a href="https://cal.com/docs/api-reference/v2/introduction">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>OAuth callback URL (optional)</td>
<td>Optional</td>
</tr>
<tr>
<td>Connection access</td>
<td>Optional</td>
</tr>
<tr>
<td>Access token</td>
<td>Optional</td>
</tr>
<tr>
<td>OAuth client ID</td>
<td>Optional</td>
</tr>
<tr>
<td>OAuth client secret</td>
<td>Optional</td>
</tr>
<tr>
<td>Return URL after authorization</td>
<td>Optional</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-calcom-users-me">
<summary><span>Read connected profile — <code>calcom.<wbr>users.<wbr>me</code></span></summary>
<p>Run <strong>Read connected profile</strong> with Cal.com. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/calcom?command=calcom.users.me">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calcom/commands/calcom.users.me">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-calcom-bookings-list">
<summary><span>List dated bookings — <code>calcom.<wbr>bookings.<wbr>list</code></span></summary>
<p>Run <strong>List dated bookings</strong> with Cal.com. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/calcom?command=calcom.bookings.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>afterStart</code></td>
<td>string</td>
<td>Required</td>
<td>Bookings starting after UTC</td>
<td><code>minLength: 20; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>beforeEnd</code></td>
<td>string</td>
<td>Required</td>
<td>Bookings ending before UTC</td>
<td><code>minLength: 20; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Results per page</td>
<td><code>minimum: 1; maximum: 20</code></td>
</tr>
<tr>
<td><code>cursor</code></td>
<td>string</td>
<td>Optional</td>
<td>Explicit page cursor</td>
<td><code>minLength: 1; maxLength: 2048; pattern: &quot;^[^\\u0000-\\u0020\\u007f]+$&quot;</code></td>
</tr>
<tr>
<td><code>status</code></td>
<td>string</td>
<td>Optional</td>
<td>Booking status</td>
<td><code>enum: [&quot;upcoming&quot;,&quot;recurring&quot;,&quot;past&quot;,&quot;cancelled&quot;,&quot;unconfirmed&quot;]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calcom/commands/calcom.bookings.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "afterStart": "2099-01-01T00:00:00Z",
  "beforeEnd": "2099-01-02T00:00:00Z",
  "limit": 5
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-calcom-event-types-list">
<summary><span>List own event types — <code>calcom.<wbr>event-<wbr>types.<wbr>list</code></span></summary>
<p>Run <strong>List own event types</strong> with Cal.com. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/calcom?command=calcom.event-types.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Maximum results</td>
<td><code>minimum: 1; maximum: 20</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calcom/commands/calcom.event-types.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "limit": 5
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-calcom-event-types-get">
<summary><span>Read own event type — <code>calcom.<wbr>event-<wbr>types.<wbr>get</code></span></summary>
<p>Run <strong>Read own event type</strong> with Cal.com. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/calcom?command=calcom.event-types.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>eventTypeId</code></td>
<td>integer</td>
<td>Required</td>
<td>Event type ID</td>
<td><code>minimum: 1</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calcom/commands/calcom.event-types.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "eventTypeId": 7
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-calcom-bookings-get">
<summary><span>Read booking — <code>calcom.<wbr>bookings.<wbr>get</code></span></summary>
<p>Run <strong>Read booking</strong> with Cal.com. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/calcom?command=calcom.bookings.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>bookingUid</code></td>
<td>string</td>
<td>Required</td>
<td>Booking UID</td>
<td><code>pattern: &quot;^[A-Za-z0-9_-]{1,200}$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calcom/commands/calcom.bookings.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "bookingUid": "fixture_booking"
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-calcom-slots-list">
<summary><span>List dated available slots — <code>calcom.<wbr>slots.<wbr>list</code></span></summary>
<p>Run <strong>List dated available slots</strong> with Cal.com. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/calcom?command=calcom.slots.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>eventTypeId</code></td>
<td>integer</td>
<td>Required</td>
<td>Event type ID</td>
<td><code>minimum: 1</code></td>
</tr>
<tr>
<td><code>start</code></td>
<td>string</td>
<td>Required</td>
<td>Range start UTC</td>
<td><code>minLength: 20; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>end</code></td>
<td>string</td>
<td>Required</td>
<td>Range end UTC</td>
<td><code>minLength: 20; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>limit</code></td>
<td>integer</td>
<td>Optional</td>
<td>Maximum results</td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calcom/commands/calcom.slots.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "eventTypeId": 7,
  "start": "2099-01-01T00:00:00Z",
  "end": "2099-01-02T00:00:00Z",
  "limit": 5
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 15 seconds.</p>

</details>
<details id="command-calcom-bookings-create">
<summary><span>Create a regular unpaid booking — <code>calcom.<wbr>bookings.<wbr>create</code></span></summary>
<p>Run <strong>Create a regular unpaid booking</strong> with Cal.com. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/calcom?command=calcom.bookings.create">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>eventTypeId</code></td>
<td>integer</td>
<td>Required</td>
<td>Event type ID</td>
<td><code>minimum: 1</code></td>
</tr>
<tr>
<td><code>durationMinutes</code></td>
<td>integer</td>
<td>Required</td>
<td>Approved duration in minutes</td>
<td><code>minimum: 1; maximum: 1440</code></td>
</tr>
<tr>
<td><code>start</code></td>
<td>string</td>
<td>Required</td>
<td>Approved start UTC</td>
<td><code>minLength: 20; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>attendee</code></td>
<td>object</td>
<td>Required</td>
<td>Approved attendee</td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>attendee.name</code></td>
<td>string</td>
<td>Required</td>
<td>Name</td>
<td><code>minLength: 1; maxLength: 200</code></td>
</tr>
<tr>
<td><code>attendee.email</code></td>
<td>string</td>
<td>Required</td>
<td>Email</td>
<td><code>maxLength: 254; format: &quot;email&quot;</code></td>
</tr>
<tr>
<td><code>attendee.timeZone</code></td>
<td>string</td>
<td>Required</td>
<td>Time zone</td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calcom/commands/calcom.bookings.create">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "eventTypeId": 7,
  "durationMinutes": 30,
  "start": "2099-01-01T08:00:00Z",
  "attendee": {
    "name": "Fixture",
    "email": "fixture@example.test",
    "timeZone": "Asia/Taipei"
  }
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-calcom-bookings-reschedule">
<summary><span>Reschedule one unpaid booking — <code>calcom.<wbr>bookings.<wbr>reschedule</code></span></summary>
<p>Run <strong>Reschedule one unpaid booking</strong> with Cal.com. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/calcom?command=calcom.bookings.reschedule">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>bookingUid</code></td>
<td>string</td>
<td>Required</td>
<td>Approved booking UID</td>
<td><code>pattern: &quot;^[A-Za-z0-9_-]{1,200}$&quot;</code></td>
</tr>
<tr>
<td><code>expectedStart</code></td>
<td>string</td>
<td>Required</td>
<td>Existing approved start UTC</td>
<td><code>minLength: 20; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>reason</code></td>
<td>string</td>
<td>Required</td>
<td>Approved reason</td>
<td><code>minLength: 1; maxLength: 500</code></td>
</tr>
<tr>
<td><code>start</code></td>
<td>string</td>
<td>Required</td>
<td>Approved new start UTC</td>
<td><code>minLength: 20; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calcom/commands/calcom.bookings.reschedule">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "bookingUid": "fixture_booking",
  "expectedStart": "2099-01-01T08:00:00Z",
  "reason": "Owner requested change",
  "start": "2099-01-02T08:00:00Z"
}
</code></pre>

<p>At most 4 provider requests per invocation; timeout: 45 seconds.</p>

</details>
<details id="command-calcom-bookings-cancel">
<summary><span>Cancel one unpaid booking — <code>calcom.<wbr>bookings.<wbr>cancel</code></span></summary>
<p>Run <strong>Cancel one unpaid booking</strong> with Cal.com. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/calcom?command=calcom.bookings.cancel">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>bookingUid</code></td>
<td>string</td>
<td>Required</td>
<td>Approved booking UID</td>
<td><code>pattern: &quot;^[A-Za-z0-9_-]{1,200}$&quot;</code></td>
</tr>
<tr>
<td><code>expectedStart</code></td>
<td>string</td>
<td>Required</td>
<td>Existing approved start UTC</td>
<td><code>minLength: 20; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>reason</code></td>
<td>string</td>
<td>Required</td>
<td>Approved reason</td>
<td><code>minLength: 1; maxLength: 500</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calcom/commands/calcom.bookings.cancel">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "bookingUid": "fixture_booking",
  "expectedStart": "2099-01-01T08:00:00Z",
  "reason": "Owner requested change"
}
</code></pre>

<p>At most 4 provider requests per invocation; timeout: 45 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://cal.com/docs/api-reference/v2/introduction">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/calcom/index.mdx