---
title: "Calendly"
description: "Read connected scheduling profiles, event types, available meeting times, busy times, meetings and invitees. Account authorization is required. Booking, cancellation, deletion and webhook changes are not enabled."
---

> 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.

# Calendly

<p>Read connected scheduling profiles, event types, available meeting times, busy times, meetings and invitees. Account authorization is required. Booking, cancellation, deletion and webhook changes are not enabled.</p>

<details data-command-index><summary>What you can do (9)</summary>
<h2>What you can do</h2>
<p>Available commands: 9 (9 read, 0 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/calendly#command-calendly-users-me">Read the connected Calendly user</a> — <code>calendly.users.me</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calendly#command-calendly-event-types-list">List a user&#39;s event types</a> — <code>calendly.event-types.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calendly#command-calendly-event-types-get">Read an event type</a> — <code>calendly.event-types.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calendly#command-calendly-event-types-available-times">Read available meeting times</a> — <code>calendly.event-types.available-times</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calendly#command-calendly-events-list">List scheduled meetings</a> — <code>calendly.events.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calendly#command-calendly-events-get">Read a scheduled meeting</a> — <code>calendly.events.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calendly#command-calendly-invitees-list">List a meeting&#39;s invitees</a> — <code>calendly.invitees.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calendly#command-calendly-invitees-get">Read a meeting invitee</a> — <code>calendly.invitees.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/calendly#command-calendly-busy-times-list">Read a user&#39;s busy times</a> — <code>calendly.busy-times.list</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/calendly">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 Calendly, then enter the issued values in the connection form below.</p>
<ol>
<li>For your account, create a Personal Access Token under Calendly Integrations &amp; apps → API and webhooks and enter Access token. For OAuth, register a developer application with the exact redirect URI, enter Client ID/Secret, save and authorize. Your plan and scopes limit scheduling access.</li>
</ol>
<p><a href="https://developer.calendly.com/">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>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-calendly-users-me">
<summary><span>Read the connected Calendly user — <code>calendly.<wbr>users.<wbr>me</code></span></summary>
<p>Run <strong>Read the connected Calendly user</strong> with Calendly. 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/calendly?command=calendly.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/calendly/commands/calendly.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-calendly-event-types-list">
<summary><span>List a user's event types — <code>calendly.<wbr>event-<wbr>types.<wbr>list</code></span></summary>
<p>Run <strong>List a user&#39;s event types</strong> with Calendly. 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/calendly?command=calendly.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>user</code></td>
<td>string</td>
<td>Required</td>
<td>Connected user URI</td>
<td><code>minLength: 1; maxLength: 200; pattern: &quot;^https://api\\.calendly\\.com/users/[A-Za-z0-9_-]{1,128}$&quot;</code></td>
</tr>
<tr>
<td><code>count</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>pageToken</code></td>
<td>string</td>
<td>Optional</td>
<td>Page token</td>
<td><code>minLength: 1; maxLength: 4096</code></td>
</tr>
<tr>
<td><code>active</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Active event types only</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

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

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

<pre><code class="language-json">{
  "user": "https://api.calendly.com/users/user_1"
}
</code></pre>

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

</details>
<details id="command-calendly-event-types-get">
<summary><span>Read an event type — <code>calendly.<wbr>event-<wbr>types.<wbr>get</code></span></summary>
<p>Run <strong>Read an event type</strong> with Calendly. 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/calendly?command=calendly.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>string</td>
<td>Required</td>
<td>Event type ID</td>
<td><code>minLength: 1; maxLength: 128; pattern: &quot;^[A-Za-z0-9_-]+$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

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

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

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

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

</details>
<details id="command-calendly-event-types-available-times">
<summary><span>Read available meeting times — <code>calendly.<wbr>event-<wbr>types.<wbr>available-<wbr>times</code></span></summary>
<p>Run <strong>Read available meeting times</strong> with Calendly. 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/calendly?command=calendly.event-types.available-times">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>startTime</code></td>
<td>string</td>
<td>Required</td>
<td>Availability start in UTC</td>
<td><code>minLength: 1; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>endTime</code></td>
<td>string</td>
<td>Required</td>
<td>Availability end in UTC</td>
<td><code>minLength: 1; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>Local result offset</td>
<td><code>minimum: 0; maximum: 10000</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>eventType</code></td>
<td>string</td>
<td>Required</td>
<td>Event type URI</td>
<td><code>minLength: 1; maxLength: 200; pattern: &quot;^https://api\\.calendly\\.com/event_types/[A-Za-z0-9_-]{1,128}$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

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

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

<pre><code class="language-json">{
  "startTime": "2099-01-01T00:00:00Z",
  "endTime": "2099-01-02T00:00:00Z",
  "eventType": "https://api.calendly.com/event_types/type_1"
}
</code></pre>

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

</details>
<details id="command-calendly-events-list">
<summary><span>List scheduled meetings — <code>calendly.<wbr>events.<wbr>list</code></span></summary>
<p>Run <strong>List scheduled meetings</strong> with Calendly. 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/calendly?command=calendly.events.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>user</code></td>
<td>string</td>
<td>Required</td>
<td>Connected user URI</td>
<td><code>minLength: 1; maxLength: 200; pattern: &quot;^https://api\\.calendly\\.com/users/[A-Za-z0-9_-]{1,128}$&quot;</code></td>
</tr>
<tr>
<td><code>count</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>pageToken</code></td>
<td>string</td>
<td>Optional</td>
<td>Page token</td>
<td><code>minLength: 1; maxLength: 4096</code></td>
</tr>
<tr>
<td><code>status</code></td>
<td>string</td>
<td>Optional</td>
<td>Meeting or invitee status</td>
<td><code>enum: [&quot;active&quot;,&quot;canceled&quot;]; minLength: 1; maxLength: 128</code></td>
</tr>
<tr>
<td><code>minStartTime</code></td>
<td>string</td>
<td>Optional</td>
<td>Earliest meeting start in UTC</td>
<td><code>minLength: 1; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>maxStartTime</code></td>
<td>string</td>
<td>Optional</td>
<td>Latest meeting start in UTC</td>
<td><code>minLength: 1; 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/calendly/commands/calendly.events.list">Full JSON Schema</a></p>

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

<pre><code class="language-json">{
  "user": "https://api.calendly.com/users/user_1"
}
</code></pre>

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

</details>
<details id="command-calendly-events-get">
<summary><span>Read a scheduled meeting — <code>calendly.<wbr>events.<wbr>get</code></span></summary>
<p>Run <strong>Read a scheduled meeting</strong> with Calendly. 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/calendly?command=calendly.events.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>eventId</code></td>
<td>string</td>
<td>Required</td>
<td>Meeting ID</td>
<td><code>minLength: 1; maxLength: 128; pattern: &quot;^[A-Za-z0-9_-]+$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

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

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

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

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

</details>
<details id="command-calendly-invitees-list">
<summary><span>List a meeting's invitees — <code>calendly.<wbr>invitees.<wbr>list</code></span></summary>
<p>Run <strong>List a meeting&#39;s invitees</strong> with Calendly. 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/calendly?command=calendly.invitees.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>eventId</code></td>
<td>string</td>
<td>Required</td>
<td>Meeting ID</td>
<td><code>minLength: 1; maxLength: 128; pattern: &quot;^[A-Za-z0-9_-]+$&quot;</code></td>
</tr>
<tr>
<td><code>count</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>pageToken</code></td>
<td>string</td>
<td>Optional</td>
<td>Page token</td>
<td><code>minLength: 1; maxLength: 4096</code></td>
</tr>
<tr>
<td><code>status</code></td>
<td>string</td>
<td>Optional</td>
<td>Meeting or invitee status</td>
<td><code>enum: [&quot;active&quot;,&quot;canceled&quot;]; minLength: 1; maxLength: 128</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

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

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

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

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

</details>
<details id="command-calendly-invitees-get">
<summary><span>Read a meeting invitee — <code>calendly.<wbr>invitees.<wbr>get</code></span></summary>
<p>Run <strong>Read a meeting invitee</strong> with Calendly. 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/calendly?command=calendly.invitees.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>eventId</code></td>
<td>string</td>
<td>Required</td>
<td>Meeting ID</td>
<td><code>minLength: 1; maxLength: 128; pattern: &quot;^[A-Za-z0-9_-]+$&quot;</code></td>
</tr>
<tr>
<td><code>inviteeId</code></td>
<td>string</td>
<td>Required</td>
<td>Invitee ID</td>
<td><code>minLength: 1; maxLength: 128; pattern: &quot;^[A-Za-z0-9_-]+$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

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

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

<pre><code class="language-json">{
  "eventId": "event_1",
  "inviteeId": "invitee_1"
}
</code></pre>

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

</details>
<details id="command-calendly-busy-times-list">
<summary><span>Read a user's busy times — <code>calendly.<wbr>busy-<wbr>times.<wbr>list</code></span></summary>
<p>Run <strong>Read a user&#39;s busy times</strong> with Calendly. 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/calendly?command=calendly.busy-times.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>user</code></td>
<td>string</td>
<td>Required</td>
<td>Connected user URI</td>
<td><code>minLength: 1; maxLength: 200; pattern: &quot;^https://api\\.calendly\\.com/users/[A-Za-z0-9_-]{1,128}$&quot;</code></td>
</tr>
<tr>
<td><code>startTime</code></td>
<td>string</td>
<td>Required</td>
<td>Availability start in UTC</td>
<td><code>minLength: 1; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>endTime</code></td>
<td>string</td>
<td>Required</td>
<td>Availability end in UTC</td>
<td><code>minLength: 1; maxLength: 24; format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>offset</code></td>
<td>integer</td>
<td>Optional</td>
<td>Local result offset</td>
<td><code>minimum: 0; maximum: 10000</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>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/calendly/commands/calendly.busy-times.list">Full JSON Schema</a></p>

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

<pre><code class="language-json">{
  "user": "https://api.calendly.com/users/user_1",
  "startTime": "2099-01-01T00:00:00Z",
  "endTime": "2099-01-02T00:00:00Z"
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 15 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://developer.calendly.com/">Official provider documentation</a></p>

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