Email API
Calendar API
Contacts API 
Scheduler
Notetaker API
Google email & calendar integration
Outlook email & calendar integration
IMAP integration
Google Meet integration
Zoom integration
Microsoft Teams integration
Docs
SDKs
Tutorials
API status
Changelog
Support
Blog
Events
Guides
Inspiration gallery
Build vs. buy
Customer stories
Security & Compliance
Why Nylas
Newsroom
Nylas Transactional Send public beta launch
• 4 min read
Today we’re launching Nylas Transactional Send into public beta, and it’s now available to all Nylas applications.
Transactional Send is the “other” way of sending emails from Nylas. When you use a Grant in Nylas to send an email, we send it through that user’s actual mailbox so that it gets sent from their account. This gives Send great deliverability, but you’re limited by how many emails the provider will let you send per day.
Transactional Send is a way to send 1:1 or 1:many emails from Nylas, without going through your Grant’s mailbox and without the provider limitations.
Sending through a Grant connected mailbox
When you send email using a Grant, messages are delivered from an individual user’s mailbox. This is ideal when emails need to come directly from a real person, like replying to messages, sending calendar invites, or participating in ongoing conversations.
Sending with Transactional Send
Transactional Send is designed for email that doesn’t depend on a user’s mailbox. Emails are sent from a verified domain, making it a better fit for product notifications, invitations, confirmations, and other outbound emails that need to scale.
Both approaches are complementary. Grant-based sending remains the best choice when you need to send as a user. Transactional Send is the better choice when you need to send as your application.
We’ve been internally using Transactional Send for the past few months for many types of emails like:
Check out our Quickstart Guide here
During the Public Beta we won’t be charging for usage, which makes it the perfect opportunity to see if this works for your application.
In order to send a transactional email you’ll need to register the sender’s domain through Nylas. This can be done through the Dashboard on the new Domains tab.
From the Domains tab you’ll register your own domain (like if you wanted to send emails from your application) or your customer’s domain (like if you wanted to send emails on their behalf).
Nylas generates the TXT & MX records for you to add to the DNS records for your domain, and once you’ve added them & we’ve verified their presence, you’ll be able to start sending out Transactional emails.
Transactional emails can be sent using the POST /v3/domains/{domain_name}/messages/send endpoint. Sending a transactional email is structured the same as sending an email from a grant’s account, but with one major difference – you need to declare who the email is from.
This code snippet shows how you send a Transactional email.
curl --request POST \
--url 'https://api.us.nylas.com/v3/domains/<DOMAIN_NAME>/messages/send' \
--header 'Accept: application/json, application/gzip' \
--header 'Authorization: Bearer <NYLAS_API_KEY>' \
--header 'Content-Type: application/json' \
--data '{
"to": [{
"name": "Jane Doe",
"email": "[email protected]"
}],
"from": {
"name": "ACME Support",
"email": "[email protected]"
},
"subject": "Welcome to ACME",
"body": "Welcome to ACME! We'\''re here to help you."
}'
Your payload should include who you’re sending the email to, who you’re sending it from (like noreply@{domain_name}, and then your subject & email body
Once you submit the payload, Nylas then sends out the transactional email from that address & to your recipient.
Transactional Send is great for applications that:
Transactional Send is now available as a public beta for all Nylas applications. Enable it through registering a domain & start sending emails in minutes.
👉 Want to try it out? Sign in to your Nylas account or create a free Sandbox account to get started.
@nylas/connect is the solution to many of the manually setup hosted authentication snippets you’ve copy‑pasted over…
Meetings should move projects forward, not create more work. Yet too often, key insights remain…
TL;DR Everyone’s doubling down it. SaaS users want to see more meeting recording capabilities in…
Product Manager