Planned for the pilot
- Google and Microsoft
- User consent and selected calendars
- Availability and users’ own single events
- Supported setup and agreed limits
RIDIAN FOR DEVELOPERS · PILOT IN PREPARATION
Calendar capabilities for your product.
Let users find free time and schedule their own events from your application. We are preparing a supported developer pilot and working with partners to define the right integration.
An individual offer. A starting point agreed together.
Your applicationPilot planned
PROJECT / PROPOSAL
Time for the next step.
Prepare proposalYour work block · 60 minutes
Check permitted calendars
Available window14:00 – 15:00
Schedule work block
Turn an intention into time on the calendar.
Connect an account
Your user signs in to Ridian, connects Google or Microsoft and chooses the allowed calendars and permissions.
Find free time
Your application checks availability across the selected calendars using that user’s permission.
Schedule a work block
The planned pilot includes creating, moving and deleting the user’s own single events. Access can be revoked.
PILOT SCOPE
A clear scope for the first step together.
We match your use case to the planned pilot. Access and technical acceptance are coordinated together.
Outside the first pilot
- Attendees and invitation delivery
- Room booking and recurring events
- Partner webhooks and a ready-made SDK
- White-label sign-in and self-service
DELEGATED ACCESS
Every integration starts with consent.
Your application receives only the access each user permits and their organisation allows. Calendar accounts stay with the user. Managing a project and accessing calendar content are separate responsibilities.
Explore security and data flowsStart with the provider. Then choose the access.
Calendar synchronisation, assistant access and partner integrations each have their own set of capabilities.
| Provider | Calendar sync | Assistants / MCP | Partner API |
|---|---|---|---|
| Available | Available · permission-dependent | Pilot planned | |
| Microsoft | Available | Available · permission-dependent | Pilot planned |
| CalDAV | Available · provider-dependent | Not available | Outside the first pilot |
“Available” refers to the supported access method. Individual actions require suitable provider permissions, user consent and, where applicable, administrator consent. CalDAV capabilities are checked per provider.
Before your integration project.
Is the partner API generally available?
No. The complete developer workflow is being prepared as a supported pilot. Ridian already has provider connections and an authorisation foundation; the pilot extends and validates the end-to-end workflow for partner applications.
Can I invite attendees or book rooms?
These are outside the first developer pilot. The planned scope covers users’ own single events without attendees. Tell us about additional requirements so we can agree the actual scope in advance.
Does my application get access to every calendar?
No. Access is determined by application permissions, user consent, provider permissions and organisation policy. Owning a project does not replace user consent.
How do we get started?
Describe your product, calendar workflow and timeframe. We will review the fit and discuss the pilot scope, technical requirements and an offer.
What should your application make possible?
Tell us about your calendar workflow. We will explore whether it fits the first developer pilot.