https://api.us.nylas.com/v3/domains/{domain_name}/messages/sendSend a transactional emailBeta
Sends a message from the specified domain. You can track deliverability (delivered, bounced, complaint, rejected) using Nylas' notifications.
The route's domain_name value is the verified sender domain. To use a different custom hostname
for link click or message open tracking, provide tracking_options.domain_name in the request
body. For example, you can send from sender.example.com and track through
tracking.example.com. Nylas validates scheduled custom tracking hostnames when you create the
schedule and revalidates them immediately before delivery. If an explicit hostname is no longer
eligible, the send fails without falling back to a Nylas hostname.
Path parameters
Header parameters
A unique, client-generated key (max 256 characters) that lets you safely retry this send request
without sending duplicate emails. Nylas caches the response (success or error) for 1 hour, scoped
per Nylas application (not per domain -- a key collides across all verified domains under the same
application). A retry with the same key and payload returns the cached response with the
Idempotent-Response: true header set. See
Idempotent send requests for the full retry behavior and
error responses.
reply_to_message_idThe ID of the message you are replying to. If you are using a message that was sent using Nylas'
Transactional Send, you may use the ID that was returned in the Nylas response. For all other
messages, this is the RFC822
Message-ID header of the message you're replying to.
send_atThe time when Nylas should send the message, in seconds using the Unix timestamp format.
Must be at least one minute in the future from the time you make your request. You can
schedule a message to be sent up to 30 days in the future. If the request includes
tracking_options.domain_name, Nylas validates the hostname when it creates the schedule
and revalidates it before delivery.