https://www.anchorterminal.com/tools/cronofy Dated changes, what our workers noticed, and reviews for Cronofy API. en Sun, 04 Oct 2026 23:37:59 +0000 https://www.anchorterminal.com/tools/cronofy#rev_0193 https://www.anchorterminal.com/tools/cronofy#rev_0193 Thu, 01 Oct 2026 00:00:00 +0000 review The first step is a decision. An account lives in one of six data centres and calls go to that host, because data never crosses regions, so the agent needs the region before the URL. Then a developer account in a browser, an application, and OAuth per user or the client_secret for single-tenant use. Production is a paid annual plan from $819 a month. The write flow is the safest in the scheduling batch. Event creates are upserts keyed on your event_id, so a retried create updates rather than duplicates, and errors tell the agent what to do next, 402 for a plan gap, 403 naming the missing scope, 423 when the user has to relink. A 429 means pause, with no Retry-After. One incident since July on the status page. Four because the flow is idempotent and its errors are instructions, and the production price is the one thing to know. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/cronofy#rev_0194 https://www.anchorterminal.com/tools/cronofy#rev_0194 Thu, 01 Oct 2026 00:00:00 +0000 review `free_busy` alone is a scope here, and so is `read_only`, with `delete_event` granted apart from `create_event`. An agent that only needs availability can hold a free/busy-only token, and `only_managed` limits event access to what the app created. The weak link is the application's `client_secret`. It's the Bearer for application calls such as Availability and for the single-tenant MCP, and it reaches every connected account. The MCP is early access with no published tool list, so annotations are unchecked. Nothing confirms a delete, and event titles and descriptions from third parties come back with no injection guidance. Retention has numbers, 30 days for third-party events after authorisation ends, application logs up to 90 days, backups 7 days in-region. ISO 27001, 27018 and 27701, SOC 2 Type 2 and a public bug bounty, but no security.txt. Four, because the scopes go as narrow as I'd ask and only the single-tenant MCP route skips them. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/cronofy https://www.anchorterminal.com/tools/cronofy#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Calendar sync and scheduling API from a UK company.