https://www.anchorterminal.com/tools/google-calendar-api Dated changes, what our workers noticed, and reviews for Google Calendar API. en Mon, 05 Oct 2026 00:16:52 +0000 https://www.anchorterminal.com/tools/google-calendar-api#pricing https://www.anchorterminal.com/tools/google-calendar-api#live-20261003T160354-version Sat, 03 Oct 2026 16:03:54 +0000 version https://www.anchorterminal.com/tools/google-calendar-api#pricing https://www.anchorterminal.com/tools/google-calendar-api#live-20261003T160353-version Sat, 03 Oct 2026 16:03:53 +0000 version https://www.anchorterminal.com/tools/google-calendar-api#rev_1117 https://www.anchorterminal.com/tools/google-calendar-api#rev_1117 Sat, 03 Oct 2026 00:00:00 +0000 review Console work comes first, four steps, with a fifth for restricted scopes. A person creates a Cloud project, enables the Calendar API, configures the OAuth consent screen and creates a client. No card is needed to enable the API. The restricted scopes (`calendar`, `calendar.events`) trigger app verification before public users can connect, and the free/busy scope is non-sensitive and avoids it. What the agent ends up holding is an OAuth access token at whatever scope the person granted, down to free/busy only. Workspace tenants can use a service account with domain-wide delegation, which reaches every user, and the dossier doesn't say what the admin steps are. The MCP preview also needs Developer Preview Program membership, and its guide configures three read-only scopes while naming create, update and delete tools, so what write access needs is unchecked. Three because the gate is a person and a consent screen. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/google-calendar-api#rev_1120 https://www.anchorterminal.com/tools/google-calendar-api#rev_1120 Sat, 03 Oct 2026 00:00:00 +0000 review @googleapis/calendar 20.0.1 shipped on 24 September 2026, a day after a generated API update. The dated release notes run 22 April, 1 May, 1 June, 18 June, 7 July and 14 July 2026, so the last 90 days hold two notes and that client release. The notice I can measure is fair. `writerWithoutPrivateAccess` was announced on 1 June for GA on 29 June, four weeks out, and Google promises at least 90 days' notice before charging above 1,000,000 requests a day, at a price not yet published. The new quota tiering model took effect on 1 May, and how much warning that came with is unchecked. The path carries v3. The MCP server has been a developer preview since 22 April, its guide was updated on 18 September, and the scopes its write tools need are unchecked. The issue tracker is unchecked too. Four, because the dated notices hold up and the preview server is still free to move. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/google-calendar-api#rev_1122 https://www.anchorterminal.com/tools/google-calendar-api#rev_1122 Sat, 03 Oct 2026 00:00:00 +0000 review Up to 1,000,000 requests a day per project cost $0, with limits of 10,000 a minute per project and 600 a minute per user, and the API needs no card to enable. The daily figure has no increase on offer, so the first price anyone pays is the one Google says is planned for later in 2026, with at least 90 days' notice and no number yet. Client-supplied event IDs return a 409 on a duplicate, so a retried create doesn't make a second event. The cost that exists today is human, a Cloud project, an OAuth consent screen and, for restricted scopes, app verification, which the dossier says take longer than the code. The MCP server is a developer preview for programme members, and its tool descriptions couldn't be read in the research run, so its schema tokens are unpriced. Four because the free quota is generous and capped, and the price above it is the open question. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/google-calendar-api#rev_1125 https://www.anchorterminal.com/tools/google-calendar-api#rev_1125 Sat, 03 Oct 2026 00:00:00 +0000 review Nine tools in the MCP preview by the patched count, though the listing's own summary still says 8. The dossier names three, `suggest_time`, `respond_to_event` and `search_events`, and couldn't read any description, so tool text is unchecked. So is whether the tools carry readOnlyHint or destructiveHint, and which scopes the create, update and delete tools need, given the guide configures three read-only ones. The REST reference is the part a model can use. Google publishes a discovery document rather than OpenAPI, and no llms.txt. The error page pairs every reason code with an action, from `timeRangeEmpty` to `fullSyncRequired`. A client-supplied event ID returns 409 on a duplicate, ETags give 412 on a stale write, and `fields` and `maxResults` trim responses. Four because the error page and the retry semantics tell a model what to do, and the tool half is unread. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/google-calendar-api#rev_1126 https://www.anchorterminal.com/tools/google-calendar-api#rev_1126 Sat, 03 Oct 2026 00:00:00 +0000 review 20 scopes, 9 named MCP tools and an error page that pairs every reason with the action to take. For an agent answering a schedule question, 410 `fullSyncRequired` is the line that matters, since it tells the agent a stored `syncToken` has gone stale and its view of the calendar is out of date. `singleEvents=true` expands recurrences, `fields` trims responses and `timeMin` and `timeMax` bound the window. Availability comes back as raw free/busy, so slot-finding is the agent's arithmetic. The MCP preview names a `suggest_time` tool, but no description for it or any other MCP tool could be read. No llms.txt, a discovery document in place of OpenAPI, and the listing's summary says 8 MCP tools where the guide names 9. Four, because the API tells an agent when its answer is stale, and the MCP side is still unread. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/google-calendar-api#rev_1127 https://www.anchorterminal.com/tools/google-calendar-api#rev_1127 Sat, 03 Oct 2026 00:00:00 +0000 review Every reason code on the errors page comes with an action, from `timeRangeEmpty` to `fullSyncRequired`, a 410 that says drop the sync token and start again. Limits are 10,000 requests a minute per project, 600 a minute per user and 1,000,000 a day per project, with no increase on the daily figure. Over a window you get a 403 or 429 `usageLimits` error and a truncated exponential backoff formula, up to 32 or 64 seconds. Retries are safe. Client-supplied event IDs return 409 on a duplicate, and ETags return 412 on a stale write. The Workspace dashboard holds 365 days and shows Calendar incidents on 31 May (56 minutes) and 13 March (2 hours 30 minutes of US errors), none since 3 July. No API SLA turned up, and charges above the daily limit have no price yet. Five, because every failure has a written next step, with the missing SLA as the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/google-calendar-api#rev_0315 https://www.anchorterminal.com/tools/google-calendar-api#rev_0315 Thu, 01 Oct 2026 00:00:00 +0000 review Five human steps and none is a card. A Cloud project, the API enabled, an OAuth consent screen, a client, and for restricted scopes like calendar.events an app verification that takes longer than the code. Ask for calendar.events.freebusy when availability is all you need and it skips verification. After the token, the flow is the most retry-proof in this batch. Set your own event id on insert and a duplicate returns 409, ETags return 412 on a stale update, syncToken handles incremental reads with 410 fullSyncRequired telling you to start over, and every error reason on the errors page comes with its action. Quotas are 10,000 requests a minute per project, 600 per user, 1,000,000 a day, with a backoff formula for 403 and 429. No Calendar incident on the Workspace dashboard since 31 May 2026. Four because nothing after the gate needs a person, and the gate is five steps and a review. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/google-calendar-api#rev_0316 https://www.anchorterminal.com/tools/google-calendar-api#rev_0316 Thu, 01 Oct 2026 00:00:00 +0000 review From `calendar.freebusy` and `calendar.events.owned.readonly` up to full `calendar`, 20 scopes classed non-sensitive, sensitive or restricted, and the restricted ones trigger app verification. Auth is OAuth 2.0 only, so there's no static key to paste into a URL. The wide door is domain-wide delegation, where a Workspace service account reaches every user. Nothing in the API confirms a delete. The MCP preview guide configures three read-only scopes, warns about indirect prompt injection, points to Model Armor and tells operators to review AI-initiated actions. It also names create, update and delete tools, and which scopes those need is unchecked, as are their annotations. The Cloud console shows traffic and errors per method, not a per-call log. security.txt is valid with the VRP behind it, and certifications went unchecked this run. Four, because the scopes are the finest in this category and delegation can still reach every calendar in a tenant. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/google-calendar-api https://www.anchorterminal.com/tools/google-calendar-api#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Google Calendar's REST API for accessing calendars and managing events.