List a Calendly user's or organization's event types
List a Calendly user's or organization's event types
Request
- x-api-key: <your-api-key>
- Content-Type: application/json
This operation is read-only. Change the path values above and send.
Response
{
"eventTypes": [
{
"active": true,
"adminManaged": true,
"bookingMethod": "POST",
"color": "#7C4DFF",
"createdAt": "2026-09-08T10:00:00Z",
"customQuestions": [
{
"answerChoices": [],
"enabled": true,
"includeOther": true,
"name": "Ada Lovelace",
"position": 10.3,
"required": true,
"type": "standard"
}
],
"deletedAt": "False",
"descriptionHtml": "<h1>Hello</h1><p>From castomAPI.</p>",
"descriptionPlain": "Generated from the endpoint's own schema.",
"duration": 6.8,
"durationOptions": [
7.5,
0.6
],
"internalNote": "<internal note>",
"isPaid": true,
"kind": "standard",
"locale": "en-GB",
"locations": [
{}
],
"name": "Ada Lovelace",
"poolingType": "standard",
"position": 10.3,
"profileName": "Ada Lovelace",
"profileOwner": "Ada Lovelace",
"profileType": "standard",
"schedulingUrl": "https://example.com/page",
"secret": true,
"slug": "my-endpoint",
"type": "standard",
"updatedAt": "2026-09-08T10:05:00Z",
"uri": "<uri>"
}
],
"nextCursor": "<next cursor>",
"status": "success",
"tokensDeducted": 1
}What it does
List a Calendly user's or organization's event types
Request
Parameters
| Field | In | Type | Required | Description |
|---|---|---|---|---|
user | query | string | no | Calendly user URI, exactly as returned by GET /v1/calendly/me. Defaults to the connected account's own user. |
organization | query | string | no | Calendly organization URI. Mutually exclusive with `user`. |
limit | query | integer | no | |
cursor | query | string | no | Opaque pagination cursor -- pass `nextCursor` from a previous response, unchanged |
accountId | query | string | no | Which connected Calendly account to use, when more than one is connected |
Response
| Field | Type | Description |
|---|---|---|
eventTypes | array<object> | |
↳ active | boolean | |
↳ adminManaged | boolean | |
↳ bookingMethod | string | |
↳ color | string | |
↳ createdAt | string | |
↳ customQuestions | array<object> | |
↳ deletedAt | string | |
↳ descriptionHtml | string | |
↳ descriptionPlain | string | |
↳ duration | number | |
↳ durationOptions | array<number> | |
↳ internalNote | string | |
↳ isPaid | boolean | |
↳ kind | string | |
↳ locale | string | |
↳ locations | array<object> | |
↳ name | string | |
↳ poolingType | string | |
↳ position | number | |
↳ profileName | string | |
↳ profileOwner | string | |
↳ profileType | string | |
↳ schedulingUrl | string | |
↳ secret | boolean | |
↳ slug | string | |
↳ type | string | |
↳ updatedAt | string | |
↳ uri | string | |
nextCursor | string | |
status | string | |
tokensDeducted | integer |
Example response
{
"eventTypes": [
{
"active": true,
"adminManaged": true,
"bookingMethod": "POST",
"color": "#7C4DFF",
"createdAt": "2026-09-08T10:00:00Z",
"customQuestions": [
{
"answerChoices": [],
"enabled": true,
"includeOther": true,
"name": "Ada Lovelace",
"position": 10.3,
"required": true,
"type": "standard"
}
],
"deletedAt": "False",
"descriptionHtml": "<h1>Hello</h1><p>From castomAPI.</p>",
"descriptionPlain": "Generated from the endpoint's own schema.",
"duration": 6.8,
"durationOptions": [
7.5,
0.6
],
"internalNote": "<internal note>",
"isPaid": true,
"kind": "standard",
"locale": "en-GB",
"locations": [
{}
],
"name": "Ada Lovelace",
"poolingType": "standard",
"position": 10.3,
"profileName": "Ada Lovelace",
"profileOwner": "Ada Lovelace",
"profileType": "standard",
"schedulingUrl": "https://example.com/page",
"secret": true,
"slug": "my-endpoint",
"type": "standard",
"updatedAt": "2026-09-08T10:05:00Z",
"uri": "<uri>"
}
],
"nextCursor": "<next cursor>",
"status": "success",
"tokensDeducted": 1
}Errors
Every error answers with the same envelope: an HTTP status, a machine code and a sentence.
400 | The body or a parameter failed validation. The details array names the field. |
401 | No key, a revoked key or a wrong header. Send x-api-key. |
402 | The wallet cannot cover this call. Top up or wait for the monthly grant. |
404 | The resource does not exist, or it is not yours. Both answer identically and cost nothing. |
429 | Over the per-minute quota of your tier. Back off and retry. |
5xx | Upstream refused or timed out. The call is not billed. |
Code
curl -X GET 'https://app.castomapi.com/v1/calendly/event-types' \ -H 'x-api-key: <your-api-key>'
const res = await fetch('https://app.castomapi.com/v1/calendly/event-types', {
method: 'GET',
headers: { 'x-api-key': '<your-api-key>' }
});
const data = await res.json();
console.log(data);import { request } from 'node:https';
// Node 18+ has fetch built in
const res = await fetch('https://app.castomapi.com/v1/calendly/event-types', {
method: 'GET',
headers: { 'x-api-key': '<your-api-key>' }
});
const data = await res.json();
console.log(data);import requests
res = requests.get(
'https://app.castomapi.com/v1/calendly/event-types',
headers={'x-api-key': '<your-api-key>'},
timeout=30,
)
print(res.json())<?php
$ch = curl_init('https://app.castomapi.com/v1/calendly/event-types');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'GET',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => ['x-api-key: <your-api-key>', 'Content-Type: application/json'],
]);
$data = json_decode(curl_exec($ch), true);
print_r($data);Cost and limits
This operation costs 1 token. A call that fails is never billed. Every account gets 1000 free tokens a month; paid balances never expire.
Rate limits per minute
| No key | 10 |
| Free | 60 |
| Pro | 300 |
| Enterprise | 1200 |
Questions
What does List a Calendly user's or organization's event types cost?
1 token per successful call, debited from your wallet after the response. Failed calls are free. Every account receives 1000 free tokens a month.
How do I authenticate?
Send your key in the x-api-key header. One key covers every metered endpoint; there is nothing to enable per endpoint.
Can I send an Authorization: Bearer token instead?
Not for a metered endpoint — those take the x-api-key header and nothing else. Bearer tokens belong to the account side: the dashboard and account APIs accept a JWT session, and castomapi-auth issues those through a standard OAuth2 handshake, with authorization code, client credentials and refresh grants. The auth service page covers it.
What are the limits?
10 requests a minute per IP with no key at all, 60 a minute on the free tier, 300 on Pro, 1200 on Enterprise. Above the no-key tier the quota is per account, across every endpoint.
OpenAPI: https://app.castomapi.com/docs/json