castomAPI
Get your key
POST /v1/calendly/scheduled-events/{uuid}/cancel 1 token API key Calendly

Cancel a Calendly scheduled event

Cancel a Calendly scheduled event. irreversible

POST

Request

  • x-api-key: <your-api-key>
  • Content-Type: application/json

Response 

{
  "cancellation": {
    "canceledBy": "<canceled by>",
    "cancelerType": "standard",
    "createdAt": "2026-09-08T10:00:00Z",
    "reason": "checksum ok"
  },
  "status": "success",
  "tokensDeducted": 1
}
The response below is a mock built from the endpoint's own schema — no request leaves this page. Edit the body, press Send, read the shape you will get back. Run it for real in the dashboard →

What it does

Cancel a Calendly scheduled event. irreversible

Request

Parameters

FieldInTypeRequiredDescription
uuidpathstringyesScheduled event uuid -- the last segment of the event URI

Body

FieldTypeRequiredDescription
accountIdstringno
reasonstringno

Example request

{
  "accountId": "acc_600444",
  "reason": "checksum ok"
}

Response

FieldTypeDescription
cancellationobject
  ↳ canceledBystring
  ↳ cancelerTypestring
  ↳ createdAtstring
  ↳ reasonstring
statusstring
tokensDeductedinteger

Example response

{
  "cancellation": {
    "canceledBy": "<canceled by>",
    "cancelerType": "standard",
    "createdAt": "2026-09-08T10:00:00Z",
    "reason": "checksum ok"
  },
  "status": "success",
  "tokensDeducted": 1
}

Errors

Every error answers with the same envelope: an HTTP status, a machine code and a sentence.

400The body or a parameter failed validation. The details array names the field.
401No key, a revoked key or a wrong header. Send x-api-key.
402The wallet cannot cover this call. Top up or wait for the monthly grant.
404The resource does not exist, or it is not yours. Both answer identically and cost nothing.
429Over the per-minute quota of your tier. Back off and retry.
5xxUpstream refused or timed out. The call is not billed.

Code

curl -X POST 'https://app.castomapi.com/v1/calendly/scheduled-events/{uuid}/cancel' \
  -H 'x-api-key: <your-api-key>' \
  -H 'Content-Type: application/json' \
  -d '{"accountId": "acc_600444", "reason": "checksum ok"}'
const res = await fetch('https://app.castomapi.com/v1/calendly/scheduled-events/{uuid}/cancel', {
  method: 'POST',
  headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
  body: JSON.stringify({"accountId": "acc_600444", "reason": "checksum ok"})
});
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/scheduled-events/{uuid}/cancel', {
  method: 'POST',
  headers: { 'x-api-key': '<your-api-key>', 'Content-Type': 'application/json' },
  body: JSON.stringify({"accountId": "acc_600444", "reason": "checksum ok"})
});
const data = await res.json();
console.log(data);
import requests

res = requests.post(
    'https://app.castomapi.com/v1/calendly/scheduled-events/{uuid}/cancel',
    headers={'x-api-key': '<your-api-key>'},
    json={"accountId": "acc_600444", "reason": "checksum ok"},
    timeout=30,
)
print(res.json())
<?php
$ch = curl_init('https://app.castomapi.com/v1/calendly/scheduled-events/{uuid}/cancel');
curl_setopt_array($ch, [
    CURLOPT_CUSTOMREQUEST => 'POST',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => ['x-api-key: <your-api-key>', 'Content-Type: application/json'],
    CURLOPT_POSTFIELDS => json_encode(['accountId' => 'acc_600444', 'reason' => 'checksum ok']),
]);
$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 key10
Free60
Pro300
Enterprise1200

Docs → Pricing

Questions

What does Cancel a Calendly scheduled event 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