Skip to content
Skip to main content

Contacts

The Nylas Contacts API allows you to create and manage contacts, and organize them into contact groups. Nylas uses the same commands to manage contacts across providers, and can refer to a specific contact using the provider's contact_id.

Contacts scopes

The table below lists the Contacts endpoints and which scopes they require. 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.

Endpoint Google Scopes
https://www.googleapis.com/auth/...
Microsoft Scopes
https://graph.microsoft.com/...
GET /contacts
GET /contacts/<CONTACT_ID>
GET /contact_groups
/contacts.readonly ☑️
/contacts.other.readonly ☑️
/directory.readonly* ☑️
Contacts.Read ☑️
People.Read* ☑️
POST /contacts
PUT /contacts/<CONTACT_ID>
DELETE /contacts/<CONTACT_ID>
/contacts ☑️ Contacts.ReadWrite ☑️
📝 Note: To access Contacts with the inbox source, you must use the contacts.other.readonly Google scope and the People.Read Microsoft scope. For Contacts with the domain source, you must use the directory.readonly Google scope and the People.Read Microsoft scope.

For more information about scopes, see Using scopes to request user data.

Contacts notifications

You can subscribe to the following triggers so Nylas notifies you about changes to your users' data:

  • contact.updated
  • contact.deleted

For more information, see the Contact notification schemas.