Create event invitee with the Calendly API
Books a meeting on an open time of an event type and returns the invitee, with event (the scheduled event URI), cancel_url and reschedule_url. Calendly sends the confirmations and calendar invites as when the invitee books on the scheduling page. Only users on a paid plan can book through the API: the Free plan gets 403.
- Identifier
- calendly_create_event_invitee
The request
POST https://connect.reportei.com/api/tools/calendly_create_event_invitee/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"event_type": "<event_type>",
"start_time": "<start_time>",
"invitee": {}
}
}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
| Parameter | Type | Required | Description |
|---|---|---|---|
| event_type | string | Yes | URI of the event type: the uri from List event types. |
| start_time | string | Yes | Start of the meeting in UTC, such as 2026-11-05T18:30:00Z: one of the start_time values from List event type available times. |
| invitee | object | Yes | The person who books the meeting. Send name, or first_name and last_name. |
| location | object | No | Where the meeting happens: one of the locations of the event type, from Get event type. Required when the event type has a location, and left out when it has none or uses round robin. |
| questions_and_answers | array | No | Answers to the booking questions, which are the custom_questions of the event type, from Get event type. Every required question must be answered. |
| tracking | object | No | UTM parameters to store with the booking. They come back in the tracking of the invitee. |
| event_guests | array | No | Email addresses of up to 10 guests to invite to the meeting. |
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_create_event_invitee. It becomes your agent's tool definition with no conversion.
Other Calendly tools
- Get current userGETReturns the connected Calendly user: uri, the user URI that List event types, List scheduled events and Create event type ask for, and current_organization, the organization URI, with name, email, scheduling_url and timezone.
- List event typesGETLists 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.
- Get event typeGETReturns one event type, with name, duration in minutes, duration_options, locations, custom_questions (the booking questions that Create event invitee answers), scheduling_url and active.
- Create event typePOSTCreates a one-on-one event type for a user and returns it. Only this kind (solo) can be created through the API, and it is created inactive unless active is true.
- Update event typePATCHUpdates a one-on-one event type and returns it. Only the fields sent change. Only event types of the solo kind can be updated through the API.
- List event type available timesGETLists the open start times of an event type in a range of up to 31 days in the future. Each item has start_time in UTC, invitees_remaining and scheduling_url. There is no pagination: ask for a shorter range when needed.
- List scheduled eventsGETLists the scheduled meetings of a user or of an organization: send user or organization. Each item has uri, name, status, start_time and end_time in UTC, event_type and invitees_counter. The response has collection and pagination: pass pagination.next_page_token as page_token to read the next page.
- Get scheduled eventGETReturns one scheduled meeting, with name, status, start_time and end_time in UTC, event_type, location, invitees_counter, event_memberships (the hosts) and, when it was canceled, cancellation.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
