Nylas · Rate Limits

Nylas Rate Limits

Published Nylas v3 rate limits, transcribed from developer.nylas.com/docs/dev-guide/platform/rate-limits/. Limits are per second and are scoped either per application or per grant, depending on the endpoint group. Nylas does not operate tier-based rate limits and does not apply a monthly request quota, so limits do not vary by plan. Nylas requests are additionally subject to the upstream provider's own limits, recorded under provider_limits below. This replaces a generated scaffold whose per-minute, per-tier values and monthly quotas did not correspond to any published Nylas limit.

Nylas Rate Limits is the machine-readable rate-limit profile for Nylas on the APIs.io network, in the API Commons Rate Limits shape.

It captures 10 rate-limit definitions, measuring requests_per_second.

Limit state is signalled in the retryAfter, providerRequestCount, and gmailQuotaUsage response headers, and an exhausted limit returns HTTP 429.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Calendar, Communication, Contacts, Email, and Messaging.

10 Limits Exhausted: HTTP 429 retryAfterproviderRequestCountgmailQuotaUsage
Published by the provider, read 2026-08-20.
View Source
CalendarCommunicationContactsEmailMessagingSchedulingRate LimitingQuotasThrottling

Limits

Applications application
requests_per_second · second
50
Authentication application
requests_per_second · second
50
Connectors application
requests_per_second · second
50
Grants application
requests_per_second · second
50
Webhooks application
requests_per_second · second
50
Calendar grant
requests_per_second · second
200
Contacts grant
requests_per_second · second
200
Messages grant
requests_per_second · second
200
Send (application/json) grant
requests_per_second · second
200
Send (multipart/form-data) grant
requests_per_second · second
10

Policies

Per-request provider fan-out
A single Nylas request can make several calls to the upstream provider. Monitor Nylas-Provider-Request-Count, and Nylas-Gmail-Quota-Usage on Google, and space requests accordingly.
Threads endpoint cost
Get all Threads makes a significant number of upstream provider calls per request. Use query parameters and a lower limit to reduce the number of results, which reduces the chance of hitting a provider limit.
Backoff strategy
Retry with exponential backoff and jitter, honoring Retry-After when present. See the avoiding-rate-limits best practices guide.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/nylas-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.