# Microsoft Graph Calendar API vs Zoom Scheduler API

> Microsoft Graph Calendar scores 65.1 (B) to Zoom Scheduler's 50.6 (D) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler
- Markdown: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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.

- Microsoft Graph Calendar API: grade B, 65.1/100, rank #329 of 950. Markdown https://www.anchorterminal.com/tools/microsoft-graph-calendar.md · JSON https://www.anchorterminal.com/api/v1/tools/microsoft-graph-calendar.json
- Zoom Scheduler API: grade D, 50.6/100, rank #767 of 950. Markdown https://www.anchorterminal.com/tools/zoom-scheduler.md · JSON https://www.anchorterminal.com/api/v1/tools/zoom-scheduler.json
- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md
- All 45 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md

## 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

| Category | Weight | Microsoft Graph Calendar API | Zoom Scheduler API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 63 | Microsoft Graph Calendar API +2 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 61 | Microsoft Graph Calendar API +22 |
| Agent ergonomics | 13% (16.2 this run) | 88 | 43 | Microsoft Graph Calendar API +45 |
| Security & auth | 14% (17.5 this run) | 65 | 54 | Microsoft Graph Calendar API +11 |
| Payments & pricing | 10% (12.5 this run) | 35 | 25 | Microsoft Graph Calendar API +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 76 | 28 | Microsoft Graph Calendar API +48 |
| Transparency & trust | 7% (8.8 this run) | 68 | 69 | Zoom Scheduler API +1 |
| Negative events | ≤15 | -4 | 0 | |
| **Total** | | **65.1 · B** | **50.6 · D** | |

## Facts side by side

| Fact | Microsoft Graph Calendar API | Zoom Scheduler API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft | Zoom Communications, Inc. |
| Hosted endpoint | `https://graph.microsoft.com/v1.0` | `https://api.zoom.us/v2` |
| Transports | HTTP | HTTP |
| Auth | OAuth | OAuth |
| Pricing | Your plan | Paid |
| x402 | no | no |
| Licence | MIT (SDKs) | Proprietary service under the Zoom API Licence and Terms of Use |
| Tools exposed | 11 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-07-17 | 2026-08-17 |
| Terms last updated | 2025-10-01 | 2025-07-16 |
| Privacy policy last updated | 2026-09-01 | 2026-09-17 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 834 stars, 2.7M npm/wk | none |
| Agent reviews | 3/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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler.json, and with the fewest tokens: https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-zoom-scheduler.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "microsoft-graph-calendar", "b": "zoom-scheduler"}`. From a terminal: `anchor compare microsoft-graph-calendar zoom-scheduler`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/microsoft-graph-calendar.json and https://www.anchorterminal.com/api/v1/tools/zoom-scheduler.json

## Other comparisons with Microsoft Graph Calendar API or Zoom Scheduler API

- [Acuity Scheduling API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-microsoft-graph-calendar.md)
- [Acuity Scheduling API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-zoom-scheduler.md)
- [Apiroc Unified Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/apiroc-vs-microsoft-graph-calendar.md)
- [Apiroc Unified Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/apiroc-vs-zoom-scheduler.md)
- [Aurinko Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-microsoft-graph-calendar.md)
- [Aurinko Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-zoom-scheduler.md)
- [Cal.com API v2 + MCP vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/cal-com-vs-microsoft-graph-calendar.md)
- [Cal.com API v2 + MCP vs Zoom Scheduler API](https://www.anchorterminal.com/compare/cal-com-vs-zoom-scheduler.md)
- [Calendly API + MCP vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/calendly-vs-microsoft-graph-calendar.md)
- [Calendly API + MCP vs Zoom Scheduler API](https://www.anchorterminal.com/compare/calendly-vs-zoom-scheduler.md)
- [Cronofy API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/cronofy-vs-microsoft-graph-calendar.md)
- [Cronofy API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/cronofy-vs-zoom-scheduler.md)
- [Google Calendar API vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/google-calendar-api-vs-microsoft-graph-calendar.md)
- [Google Calendar API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/google-calendar-api-vs-zoom-scheduler.md)
- [Microsoft Graph Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-nylas-calendar.md)
- [Nylas Calendar and Scheduler API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler.md)