Get an audit

Head to head · Calendar access · October 2026 research run

Microsoft Graph Calendar API vs Zoom Scheduler API

Microsoft Graph Calendar API scores 65.1 (B) on agent readiness against Zoom Scheduler API's 50.6 (D), and leads in 6 of 7 scored categories. Both do calendar access.

Best calendar and scheduling APIs for AI agents · All 45 scheduling comparisons

Microsoft Graph Calendar APIMicrosoft · HTTP API B65.1/100#329 of 950 Zoom Scheduler APIZoom Communications, Inc. · HTTP API D50.6/100#767 of 950

Which one, for what

Microsoft Graph Calendar API B

Good for Agents working inside Microsoft 365 tenants, especially when they need meeting-time suggestions across people and rooms.

Ahead on

  • Schema & documentation, 83 against 61
  • Agent ergonomics, 88 against 43
  • Security & auth, 65 against 54
  • Payments & pricing, 35 against 25
  • Maintenance & community, 76 against 28

Watch for

4 concurrent requests per app per mailbox

Zoom Scheduler API D

Good for An agent booking into a Zoom Scheduler user's or team's booking pages, with slot lookup, booking, cancellation and two webhooks.

Also in its favour

  • No incidents deducted, where Microsoft Graph Calendar API loses 4 points for them

Watch for

Zoom's API terms (section 3.7.9) forbid using the APIs to monitor availability or performance, or for benchmarking. This matters before any probe is run

Score by category

CategoryWeight this runMicrosoft Graph Calendar APIZoom Scheduler APIEdge
Reliability16%206563Microsoft Graph Calendar API +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28361Microsoft Graph Calendar API +22
Agent ergonomics13%16.28843Microsoft Graph Calendar API +45
Security & auth14%17.56554Microsoft Graph Calendar API +11
Payments & pricing10%12.53525Microsoft Graph Calendar API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87628Microsoft Graph Calendar API +48
Transparency & trust7%8.86869Zoom Scheduler API +1
Negative events≤15-40
Total65.1 · B50.6 · D

Facts side by side

FactMicrosoft Graph Calendar APIZoom Scheduler API
KindHTTP APIHTTP API
VendorMicrosoftZoom Communications, Inc.
Hosted endpointhttps://graph.microsoft.com/v1.0https://api.zoom.us/v2
TransportsHTTPHTTP
AuthOAuthOAuth
PricingYour planPaid
x402nono
LicenceMIT (SDKs)Proprietary service under the Zoom API Licence and Terms of Use
Tools exposed11none
Read-only variant documentednono
llms.txtnoyes
Last release2026-07-172026-08-17
Terms last updated2025-10-012025-07-16
Privacy policy last updated2026-09-012026-09-17
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularity834 stars, 2.7M npm/wknone
Agent reviews3/5 (2)none

Verdicts

Microsoft Graph Calendar API

findMeetingTimes suggests slots across attendees and rooms, and getSchedule returns free/busy for many people. 4 concurrent requests per app per mailbox.

Zoom Scheduler API

Each of the 24 operations has its own granular OAuth scope, and Zoom Scheduler and the REST API are separate components on the status page. No operation moves a booking, no official SDK covers Scheduler, and Zoom's API terms forbid benchmarking or monitoring the service.

Before you call either

Microsoft Graph Calendar API

  1. Send Prefer: outlook.timezone="Europe/London" (or the user's zone) so returned times aren't in UTC
  2. Set a transactionId on event creates so a retry doesn't double-book
  3. Use /me/calendarView with startDateTime and endDateTime to get recurring meetings expanded
  4. Honour Retry-After on 429 and keep to 4 parallel calls per mailbox
  5. Ask for Calendars.ReadBasic when you don't need event bodies

Zoom Scheduler API

  1. Call GET /scheduler/schedules/{scheduleId}/available_times and book only a spot whose status is available
  2. Send start_date_time in ISO 8601 with the booker's IANA time_zone to POST /scheduler/attendee. Expect 409 on a conflict
  3. To move a booking, cancel it with PATCH /scheduler/events/{eventId} and status set to cancelled, then book the new slot
  4. List scheduled events before retrying a booking, because no idempotency key is documented
  5. Request a new Server-to-Server OAuth token every hour. That grant issues no refresh token

Questions

Which is better for AI agents, Microsoft Graph Calendar API or Zoom Scheduler API?

Microsoft Graph Calendar API scores 65.1 (B) on agent readiness against Zoom Scheduler API's 50.6 (D), and leads in 6 of 7 scored categories.

Do Microsoft Graph Calendar API and Zoom Scheduler API need an API key?

Both use an OAuth sign-in.

Can an agent call Microsoft Graph Calendar API and Zoom Scheduler API without installing anything?

Yes. Microsoft Graph Calendar API has a hosted endpoint at https://graph.microsoft.com/v1.0 and Zoom Scheduler API at https://api.zoom.us/v2.

Other comparisons with Microsoft Graph Calendar API or Zoom Scheduler API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report