List event types with the Calendly API

Lists the event types of a user or of an organization: send user or organization. Each item has uri, name, duration in minutes, scheduling_url and active. The response has collection and pagination: pass pagination.next_page_token as page_token to read the next page.

Identifier
calendly_list_event_types

The request

POST https://connect.reportei.com/api/tools/calendly_list_event_types/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "user": "<user>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
userstringNoURI of the user whose event types to list: the uri from Get current user. Send user or organization.
organizationstringNoURI of the organization, to list all of its event types: the current_organization from Get current user. Send user or organization.
activebooleanNotrue for only the active event types, false for only the inactive ones. Omit it for all.
admin_managedbooleanNotrue for only the event types managed by an admin, false to leave them out. Omit it for all.
sortstringNoComma-separated field:direction pairs. The fields are name, position, created_at and updated_at, and the direction is asc or desc. The default is name:asc.
page_tokenstringNoThe pagination.next_page_token of the previous response, sent with the same filters.
countintegerNoEvent types per page, up to 100. The default is 20.

Supported connections

Your customer connects their Calendly account once, with one of the modes below. The same connection serves every tool of the toolkit.

OAuth with your product's app

You register your product's OAuth app once, with POST /api/merchants/credentials/calendly, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/calendly_list_event_types. It becomes your agent's tool definition with no conversion.

Other Calendly tools

See all 12 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.