Nylas API

Name: Nylas API
Brand: Nylas API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail Deliverybearer55 EndpointsREST

For Agents

Read and write across users' email, calendars, and contacts on Google, Microsoft, and IMAP from a single unified API with bearer authentication and hosted auth.

Install Jentic One Beta

Connect the Nylas API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nylas API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Nylas API.

Run a hosted OAuth-style flow that returns a long-lived grant for a user's mailbox

Send, list, and reply to email messages and manage drafts on the user's behalf

Create, update, and delete calendar events with attendee and recurrence handling

GET STARTED

Start building with Nylas API

Explore with Jentic

View OpenAPI Document

The Nylas API v3 provides a unified communications surface across email, calendar, and contacts that abstracts away the differences between Google, Microsoft, and IMAP backends. The 55-endpoint API covers OAuth-style hosted authentication, grant management, connector configuration, and full read/write operations on messages, threads, drafts, events, calendars, and contacts. It is well suited to building scheduling tools, inbox-aware AI assistants, and CRM enrichment workflows that need to read and write across whichever email and calendar provider the end user happens to use.

Use Cases

Patterns agents use Nylas API for, with concrete tasks.

★ AI Scheduling Assistant

Build a meeting-scheduling assistant that reads a user's calendar, proposes free slots, and creates events with the right attendees, regardless of whether the user is on Google or Microsoft. The unified events and grants endpoints mean one code path covers both backends, and the hosted auth flow handles consent. A working scheduling integration is achievable in 1-2 days from a fresh Nylas account.

GET /v3/grants/{grantId}/calendars/free-busy for the next five days, pick a 30-minute slot, then POST /v3/grants/{grantId}/events with the chosen time and attendees.

Inbox-Aware AI Assistant

Create an inbox copilot that summarises long threads, drafts replies, and triages on the user's behalf. Nylas exposes messages, threads, and drafts through a consistent shape, so an LLM-backed assistant can read context and write replies through the same interface across providers. This avoids maintaining separate Gmail and Microsoft Graph integrations.

List the user's unread messages via /v3/grants/{grantId}/messages, summarise the top thread, and create a draft reply via POST /v3/grants/{grantId}/drafts.

CRM Contact Enrichment

Sync a user's contacts and recent email correspondents into a CRM to keep records up to date without manual entry. Nylas's contact endpoints, combined with thread participants from the messages API, provide a richer signal than a contacts-only sync. This is a common pattern for sales-engagement tools and lightweight CRMs.

List contacts via /v3/grants/{grantId}/contacts and upsert each into the CRM, deduplicating on email address.

Agent-Driven Communication Across Providers

Let an AI agent send a message or schedule a meeting for a user without caring whether the underlying account is Google or Microsoft. Through Jentic, the agent searches by intent and gets only the operations it needs, with grant tokens held in the platform's vault rather than in the agent's context.

Search Jentic for 'send an email from a user mailbox', load the operation, and send a follow-up email referencing yesterday's meeting.

Key Endpoints

55 endpoints — the nylas api v3 provides a unified communications surface across email, calendar, and contacts that abstracts away the differences between google, microsoft, and imap backends.

METHOD

PATH

DESCRIPTION

POST

/v3/connect/auth

Start the hosted OAuth flow

POST

/v3/connect/token

Exchange the auth code for a grant token

GET

/v3/grants

List grants in a Nylas application

DELETE

/v3/grants/{grantId}

Revoke a grant

POST

/v3/connectors

Create a connector for a backend provider

POST

/v3/connect/auth

Start the hosted OAuth flow

POST

/v3/connect/token

Exchange the auth code for a grant token

GET

/v3/grants

List grants in a Nylas application

DELETE

/v3/grants/{grantId}

Revoke a grant

POST

/v3/connectors

Create a connector for a backend provider

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Nylas API key and per-user grant tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send an email from a user mailbox' or 'create a calendar event', and Jentic returns the matching Nylas operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Nylas API through Jentic.

What authentication does the Nylas API use?

Nylas uses bearer authentication. Application-level calls send your Nylas API key in the Authorization header; per-user calls send the grant token issued by the hosted auth flow at /v3/connect/auth and /v3/connect/token. Through Jentic, both keys and grant tokens are stored encrypted in the vault.

Does Nylas support Microsoft and Google in one API?

Yes - that is the core value. The same /v3/grants/{grantId}/messages, /events, and /contacts paths work across Google Workspace, Microsoft 365, and IMAP backends, with the difference handled by Nylas's connector layer.

What are the rate limits for the Nylas API?

The OpenAPI spec does not embed explicit limits. Nylas applies per-application and per-grant throttling that varies by plan; back off on HTTP 429 and the X-RateLimit-* response headers when present.

How do I send an email from a user's mailbox through Jentic?

Run pip install jentic, then search for 'send an email from a user mailbox'. Jentic returns the messages-send operation with its input schema; supply the grant id, recipients, subject, and body and execute. Run it through Jentic One, the self-hosted execution layer, to get an agent API key.

Can I find a free time slot for a user?

Yes - the free/busy endpoints expose availability for the user's connected calendars across providers, so an agent can pick a slot before posting an event via POST /v3/grants/{grantId}/events.

Can I limit what my agent is allowed to do with the Nylas API?

Yes. Because you run Jentic One yourself, your own rules decide which Nylas operations and which credentials the agent may use at execution time. Since Nylas puts the grant id in the URL path (/v3/grants/{grantId}), you can pin the agent to just the operations it needs, for example authenticating connections and reading grants, messages, and events, while a destructive call like grant deletion stays out of reach unless you explicitly add it. You choose the exact set of operations the agent can call.

Nylas API

Connect the Nylas API to your agent

Capabilities

Start building with Nylas API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs