Message Streams let you classify application email as Transactional or Broadcast. Streams belong to a sending domain and can also be assigned to email templates.
Every sending domain receives a built-in
transactional stream automatically. If
message_stream is omitted from a send request,
Sendzovo uses the domain's default Transactional stream.
Stream types
| Type | Use | Unsubscribe URL |
|---|---|---|
| Transactional | Application-triggered messages such as account, security, billing and notification email. | Not required by the Sendzovo API. |
| Broadcast | Application email intentionally sent through a Broadcast stream. |
Required. Supply unsubscribe_url
with the send request.
|
Select a stream
Supply the stream slug using message_stream.
The stream must belong to the same sending domain as the
Sending API key.
{
"from": "notifications@example.com",
"to": [
{
"email": "customer@example.net"
}
],
"subject": "Account notification",
"html": "<p>Your account was updated.</p>",
"message_stream": "transactional"
}Broadcast example
{
"from": "updates@example.com",
"to": [
{
"email": "customer@example.net"
}
],
"subject": "Product update",
"html": "<p>Here is our latest product update.</p>",
"message_stream": "product-updates",
"unsubscribe_url": "https://example.com/unsubscribe/customer-token"
}
A request using a Broadcast stream is rejected if
unsubscribe_url is missing.
Templates and streams
A template can be assigned to a Message Stream. When a template with an assigned stream is used for sending, Sendzovo uses that template's stream. The stream must be available and belong to the sending domain.
Create a free Sendzovo account, verify your domain and send your first email in minutes.