Virtual Calendars work like any other calendar and make it easy to embed customized scheduling functionality into your application. They're ideal for situations where you need to schedule events for people or objects that aren’t associated with an existing calendar account. Virtual Calendars allow you to provide scheduling functionality to your users without requiring them to connect a third-party service provider like Google, Exchange, or Office 365. There are two major scheduling use cases for virtual calendars:
- Users who have sensitive data in their personal calendar that they don't want to expose to do their task.
- People or resources that don't have an account on a third-party service provider
Virtual calendars behave much like any other user calendar and they can be used for most scheduling scenarios. Let's take a look at how they work.
When you create a Virtual Calendar the
"name": "Virtual Calendar",
Virtual Accounts can be leveraged as a part of any new or existing Nylas app. They are only available with Native Auth, and you need to provide the Nylas app’s
client_id to authenticate them. Each application can have multiple virtual accounts with the associated virtual calendar. Once you create the Virtual Account and Virtual Calendar you can treat them like any other user calendar.
Virtual Calendars do not send out invitations. To send invites, use the Generate ICS file endpoint.
In your dashboard it will appear as an account with the Provider: Nylas.
Virtual Calendar Limit
Each virtual account is limited to one virtual calendar.
Virtual Calendars supports the following webhooks:
- Scheduler does support Virtual Calendars.
- Virtual Calendars use Native Authentication only.
- Virtual Calendars support notifications.
- Virtual Calendars only works with
- Each Virtual Account is limited to one Virtual Calendar.