This page lists the Email 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.
Email API scopes
| Endpoint |
Google Scopes
https://www.googleapis.com/auth/...
|
Microsoft Scopes
https://graph.microsoft.com/...
|
|---|---|---|
|
| |
|
| |
|
| |
POST |
|
|
POST |
|
|
|
| |
|
| |
|
| |
|
| |
POST |
|
|
|
| |
GET | No scopes are required because scheduled messages are stored with Nylas. To send scheduled messages, you need | |
Email API scopes for Yahoo OAuth
If you use Yahoo OAuth authentication to connect to Yahoo users’ email inboxes, include the following scopes in your Yahoo provider auth app.
📝 Note: All Email notifications require the Yahoo email and mail-r scopes.
Email notification scopes
| Notification trigger | Google Scopeshttps://www.googleapis.com/auth/... | Microsoft Scopeshttps://graph.microsoft.com/... |
|
| |
|
| |
|
| |
|
| |
|
|