Calendar and Events scopes
This page lists the Calendar and Events API endpoints and notification triggers available in Nylas v3, and shows which scopes they require. For more information about scopes in Nylas v3, see the Authentication scopes documentation.
All scopes must include the fully qualified URI path for the provider. The table shortens the full scope URI for space reasons, so add the prefix for the provider when requesting scopes.
The ☑️ in each column indicates the most restrictive scope you can request for each provider and still use that API. More permissive scopes appear under the minimum option. If you're already using one of the permissive scopes, you don't need to add the more restrictive scope.
Calendar and Events API scopes
| Endpoint | Google Scopeshttps://www.googleapis.com/auth/... | Microsoft Scopeshttps://graph.microsoft.com/... |
|
GET |
|
|
|
POST |
|
|
|
POST |
|
|
|
GET |
|
|
|
POST |
|
|
|
POST |
|
|
|
GET |
|
|
| Automatic conferencing creation |
Microsoft Teams: | |
Calendar and Events notification scopes
| Notification trigger | Google Scopeshttps://www.googleapis.com/auth/... | Microsoft Scopeshttps://graph.microsoft.com/... |
|
|
|
|
|
|
|
|
For more information about Calendar and Events notifications, see the Calendar and Events notification schemas.