Build on the calendar layer

Choose your interface

MCP exposes calendar, availability and supported action tools to authorized assistants and applications. REST currently exposes the published calendar and event read endpoints. Both enforce Ridian’s effective permissions; neither is an escape hatch around workspace policy.

Start with authentication, then inspect the REST reference or MCP tool reference. A user’s calendar data requires that user’s delegated authorization.

Know the current product boundary

The partner platform is under development. Self-service projects, managed test/live clients, expanded REST writes, outgoing partner webhooks and SDKs are not generally available. Provider webhooks used internally by sync are not outgoing notifications for your application.

Discuss a partner workflow with Ridian before building against a planned endpoint. The current pilot direction is a user connecting their calendar, finding time and managing a standalone event without guests; the broader partner lifecycle has its own acceptance requirements.

Design around real provider behavior

Permission, recurrence, time zone and event capability differences do not disappear behind a unified interface. Preserve opaque IDs, use explicit time offsets, handle revocation and never treat a provider failure as free time. Read errors and retries before enabling writes.