canonical: https://jentic.com/apis/allmymeetings.com/allmymeetings # AllMyMeetings API The AllMyMeetings API exposes calendar operations through a single authenticated JSON-RPC endpoint and keeps connected calendars in sync by receiving real-time change notifications from Google Calendar and Microsoft Graph. The JSON-RPC endpoint provides calendar event management, sync-pair management, scheduling links, availability lookups, and conflict detection, authenticated with a Sanctum personal access token. Inbound provider webhooks push calendar changes, a Stripe webhook handles billing events, and well-known discovery documents advertise the server card and an API catalog linkset. It is a hub for agents that need to read and manage calendars across Google and Microsoft accounts. ## For AI agents Manage calendars across Google and Microsoft accounts through one authenticated JSON-RPC endpoint: create and update events, manage sync pairs and scheduling links, look up availability, and detect conflicts. Provider webhooks keep connected calendars in sync. ## Scope Does not host video calls, send email, or transcribe meetings. Use for calendar operations, cross-provider sync, scheduling links, and availability only. ## Capabilities - Create, update, and remove calendar events across connected Google and Microsoft accounts - Manage sync pairs that mirror events between two calendars - Create and manage scheduling links for booking meetings - Look up availability and detect scheduling conflicts before booking - Receive real-time calendar change notifications from Google Calendar and Microsoft Graph via webhooks - Serve discovery documents including a server card and an API catalog linkset ## Use cases ### Agent Scheduling Across Calendars An assistant agent can look up availability, detect conflicts, and create an event across a user's connected Google and Microsoft calendars through one JSON-RPC endpoint, without wiring each provider separately. Because the endpoint also exposes scheduling links and sync pairs, the agent can hand out a booking link or mirror an event between calendars in the same flow. This lets an agent own meeting scheduling end to end over a single integration. Example prompt: Look up availability for a one-hour slot this week, detect conflicts, and create the event on the user's primary connected calendar. ### Keeping Calendars in Sync AllMyMeetings receives push notifications from Google Calendar and Microsoft Graph, so changes made in one place propagate without polling, and sync pairs mirror events between two calendars. An agent sets up a sync pair and then relies on the inbound webhooks to keep both sides current. This keeps a unified view of meetings accurate as events change at the source. Example prompt: Create a sync pair between a work and a personal calendar so events created in one are mirrored to the other. ### Offering a Booking Link The endpoint exposes scheduling links so an agent can generate a shareable link that respects the user's real availability and conflict rules. A recipient books into an open slot, and the resulting event lands on the connected calendar. This gives an agent a self-service booking surface without building a scheduling page. Example prompt: Generate a scheduling link for a 30-minute meeting that reflects the user's current availability and conflict rules. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/mcp/calendar` | Authenticated JSON-RPC calendar endpoint exposing calendar, sync, availability, and conflict tools | | POST | `/api/webhooks/google` | Inbound Google Calendar push notification | | POST | `/api/webhooks/microsoft` | Inbound Microsoft Graph change notification | | POST | `/api/webhooks/stripe` | Inbound Stripe billing event | | GET | `/.well-known/mcp/server-card.json` | Server card discovery document | | GET | `/.well-known/api-catalog` | API catalog linkset | ## Key resources - **Calendar Endpoint** — A single authenticated JSON-RPC endpoint exposing calendar event management, sync pairs, scheduling links, availability, and conflict detection - **Provider Webhooks** — Inbound push notifications from Google Calendar and Microsoft Graph that keep connected calendars in sync - **Billing Webhook** — A Stripe webhook endpoint that handles billing events - **Discovery** — Well-known documents advertising the server card and an API catalog linkset ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 65 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 84 / 100 - Developer Experience & Jentic Compatibility: 57 / 100 - AI-Readiness & Agent Experience: 48 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 81 / 100 - **View full report:** https://jentic.com/apis/allmymeetings.com/allmymeetings/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the AllMyMeetings API by hand means minting a Sanctum personal access token, sending it as a bearer token on the calendar endpoint, and leaving the inbound provider and billing webhooks open for the providers to call. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls the calendar operations. - **Permission scoping:** A rule can allow your agent only the operations it needs: for example the public discovery reads without the authenticated calendar endpoint, or the calendar endpoint itself. The individual calendar tools travel as methods inside the JSON-RPC request body, so rules bound which endpoints the agent may call rather than which tool inside the calendar endpoint. - **Credential handling:** Your AllMyMeetings Sanctum token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'check availability and create an event' or 'set up a calendar sync pair', and Jentic returns the matching AllMyMeetings operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Nylas** — Unified calendar and email API across providers rather than a JSON-RPC calendar hub with sync pairs - **Cronofy** — Cross-provider scheduling and availability API as a REST surface instead of a single JSON-RPC endpoint - **Calendly** — Dedicated booking pages that complement AllMyMeetings' own scheduling links ## FAQ ### What authentication does the AllMyMeetings API use? Per its OpenAPI spec the calendar JSON-RPC endpoint uses an HTTP bearer scheme carrying a Sanctum personal access token, which you mint at the settings API page and send in the Authorization header. The inbound provider and billing webhook endpoints and the well-known discovery documents are not gated by your token, since they are called by the providers or served publicly. ### What calendar operations can I run with the AllMyMeetings API? The JSON-RPC endpoint exposes calendar event management, sync-pair management, scheduling links, availability lookups, and conflict detection across connected Google and Microsoft accounts. You call these as methods on the single calendar endpoint rather than as separate REST paths. ### What are the rate limits for the AllMyMeetings API? The OpenAPI spec does not publish numeric rate limits for the AllMyMeetings API. For current limits check the vendor documentation at https://allmymeetings.com. ### How do I schedule a meeting with the AllMyMeetings API through Jentic? Import the AllMyMeetings API from the Jentic API Directory, then have your agent search by intent such as 'check availability and create an event' and Jentic returns the calendar endpoint with its input schema. The agent looks up availability, detects conflicts, and creates the event. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the AllMyMeetings API? Yes. Write a rule that allows only the public discovery reads, so your agent can fetch the server card and API catalog but cannot touch your calendar, or allow the calendar endpoint when you want it to manage events. The specific calendar tool is named inside the JSON-RPC request body, so a rule governs which endpoints the agent may call, and every call it makes is logged. ### Is there an AllMyMeetings MCP server? Yes. AllMyMeetings is built around a Model Context Protocol server for calendar operations, and its discovery documents advertise a server card for MCP-aware clients. You can also connect it through Jentic: your token is injected at call time by your self-hosted instance instead of living in a client config, your rules decide which operations the agent may call, and connecting the next API is an import rather than another install. ### Which calendar providers does the AllMyMeetings API support? The spec shows inbound change notifications from Google Calendar and Microsoft Graph, so connected calendars on both providers stay in sync. Sync pairs then let you mirror events between two of the connected calendars.