Only show these results:

How Nylas Works

Nylas API and Sync Architecture Overview

The Nylas API makes it easy to connect and sync mail, calendar, and contact data from any email service provider. Below is a diagram that shows how your application can use the Nylas API to sync data from providers such as GSuite and Microsoft:

Nylas Architecture Diagram

Data Storage

When you authenticate an account to Nylas, our sync servers automatically start syncing mail, calendar, and contact data from the provider into the Nylas database. Mail, contact, and calendar data is stored for up to 30 days.

Nylas syncs 30 days of data by default. You can adjust this by updating your historical sync settings.

We also cache files, attachments, and copies of the raw RFC-2822 MIME message in an Amazon S3 bucket for seven days. If you request the raw message within the first seven days, we'll return our cached copy from S3. After that, we'll delete the extra copy of the raw message from S3, and any further requests for the data will be proxied to the original mail server to re-retrieve the original data.

Performance

Performance Estimation

The statistics below are approximations and actual performance may vary per provider. These serve to provide a rough estimate when thinking about designing your application with our API. Please reference your service agreement for specific guarantees regarding performance.

Metric Value Description
API Success Rate 99.9% The number of requests that return successful HTTP status codes
P90(request_time) Less than 500 ms P90 of request_time to various API endpoints
TT50 5 min The average time it takes to sync the first 50 threads for an account during the initial sync
TT500 25 min The average time it takes to sync the first 500 threads for an account during the initial sync
Historical Sync Time 1 day The average time it takes to sync all historical mail for an account. This is highly variable depending on how much data the account has and the upstream bandwidth of the mail server