How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Nylas Messages API

Messages. List, search, read, update and delete email messages. Send immediately, schedule a send and cancel a scheduled send, with folders, signatures and attachments alongside.

Nylas Messages API is one of 13 APIs that Nylas publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Message. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 24 operations across 15 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version v3.

Requests are made against 2 base URLs: https://api.us.nylas.com, https://api.eu.nylas.com.

24 operations 15 paths 22 schemas 4 DELETE10 GET6 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3
Base URL
https://api.us.nylas.com
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Nylas Messages API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (NYLAS_ACCESS_TOKEN) (ACCESS_TOKEN). It accepts HTTP bearer tokens (NYLAS_API_KEY) (NYLAS_API_KEY). By default, every request must be authenticated.

  • ACCESS_TOKEN — The Nylas access token for a specific grant. Issued as part of OAuth 2.1 flow token exchange.
  • NYLAS_API_KEY — The Nylas API key provides application-level access to APIs and all grants. You can generate these from the Dashboard. Learn more about [authorizing requests](…

Paths & Operations 24

Across 15 paths, the API surfaces 24 operations — 4 DELETE, 10 GET, 6 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Messages 24
GET
/v3/grants/{grant_id}/messages
Return all Messages
get-messages 23 params → 200400401429504
GET
/v3/grants/{grant_id}/messages/{message_id}
Return a Message
get-messages-id 6 params → 200400401404429504
PUT
/v3/grants/{grant_id}/messages/{message_id}
Update message attributes
put-messages-id 5 params body → 200400401404429504
DELETE
/v3/grants/{grant_id}/messages/{message_id}
Delete a message
delete-message 4 params → 200400401404429504
PUT
/v3/grants/{grant_id}/messages/clean
Clean messages
clean-messages 3 params body → 200400401404429504
POST
/v3/grants/{grant_id}/messages/send
Send a Message
send-message 3 params body → 200202400403409429504
GET
/v3/grants/{grant_id}/messages/schedules
Return scheduled messages
get-schedules 1 param → 200
GET
/v3/grants/{grant_id}/messages/schedules/{scheduleId}
Return a scheduled message
get-schedule-by-id 2 params → 200404
DELETE
/v3/grants/{grant_id}/messages/schedules/{scheduleId}
Cancel a scheduled message
delete-a-scheduled-message 2 params → 202404
GET
/v3/grants/{grant_id}/folders
Return all folders
get-folder 8 params → 200400401429504
POST
/v3/grants/{grant_id}/folders
Create a Folder
post-folder 3 params body → 200400401429504
GET
/v3/grants/{grant_id}/folders/{folder_id}
Return a Folder
get-folders-id 5 params → 200400401404429504
PUT
/v3/grants/{grant_id}/folders/{folder_id}
Update a folder
put-folders-id 5 params body → 200400401404429504
DELETE
/v3/grants/{grant_id}/folders/{folder_id}
Delete a Folder
delete-folders-id 3 params → 200400401404429504
GET
/v3/grants/{grant_id}/signatures
Return all signatures
list-signatures 4 params → 200400401429504
POST
/v3/grants/{grant_id}/signatures
Create a signature
post-signature 2 params body → 201400401429504
GET
/v3/grants/{grant_id}/signatures/{signature_id}
Return a signature
get-signature 3 params → 200400401404429504
PUT
/v3/grants/{grant_id}/signatures/{signature_id}
Update a signature
put-signature 3 params body → 200400401404429504
DELETE
/v3/grants/{grant_id}/signatures/{signature_id}
Delete a signature
delete-signature 2 params → 200400401404429504
POST
/v3/domains/{domain_name}/messages/send
Send a transactional email
send-transactional-email 2 params body → 200400409
GET
/v3/grants/{grant_id}/attachments/{attachment_id}
Return Attachment metadata
get-attachments-id 5 params → 200400401404429504
GET
/v3/grants/{grant_id}/attachments/{attachment_id}/download
Download an Attachment
get-attachments-id-download 4 params → 200400401404429504
POST
/v3/grants/{grant_id}/attachment-uploads
Create an attachment upload session
create-attachment-upload-session 1 param body → 201400401500
POST
/v3/grants/{grant_id}/attachment-uploads/{attachment_id}/complete
Complete an attachment upload session
complete-attachment-upload-session 2 params → 200401404409410422500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are message (22 properties), message_send_response (22 properties), folder (13 properties), transactional_send_message (12 properties). Each schema is shown below with its type and property counts.

message_send_response
object
22 properties
object
string
The type of object.
signature
object
7 properties
attachment
object
A file attached to an email message.
8 properties 1 required
message-header
object
A message header key-value pair.
2 properties 2 required
transactional_send_message
object
12 properties
Schedules
object
3 properties 2 required
grant_id
string
The ID of grant for the connected user.
common_response_with_cursor
object
3 properties
message
object
22 properties
folder
object
An email folder or label.
13 properties
common_response
object
2 properties
metadata
object
The metadata associated with the object. For more information, see [Metadata](/docs/reference/api/metadata).
attachment_transactional_send
object
A file attachment for a transactional email message.
6 properties
id
string
A globally unique object identifier for Microsoft accounts. An email address for Google accounts.
message-participant
object
A name/email address pair.
2 properties 1 required
message-participant-response
object
A name/email address pair.
2 properties
create_folder
object
4 properties 1 required
update_folder
object
4 properties
tracking_domain_name
string
The custom hostname to use for link click and message open tracking. The hostname must be registered to the authenticated organization in the [Nylas Dashboard]…
attachment_metadata
object
Metadata for a file attached to an email message.
8 properties
use_draft
boolean
(Google and Microsoft only) If true when scheduling a message, Nylas saves the message in the user's Drafts folder until it's sent. For more information, see […

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nylas-messages-api-openapi.yml Raw ↑

Other APIs Nylas publishes across the network.

Nylas Admin API
Nylas Auth API
Nylas Calendars API
Nylas Contacts API
Nylas Drafts API
Nylas Events API
Nylas Grants API
Nylas Scheduling API
Nylas Threads API
Nylas Notifications API
Nylas Notetaker API
Nylas Templates and Workflows API
Where this information came from

This is an independent, third-party profile of Nylas Messages API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.