---
schema_version: "1"
id: 7353f2fba3779326d72f46622cc011b72a22478de0396b93a9f338abe1b0e988
title: Send Transactional Messages with Direct Email Send API
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/marketing-cloud/mc-core/guide/mc-manage-transactional-messages/mc-manage-transactions-messages-direct-send.md
canonical_url: https://developer.salesforce.com/docs/marketing/marketing-cloud-growth/guide/mc-manage-transactions-messages-direct-send.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 8e634e84eec6d62699c76b14f672d540a0854c766e0253db8b79ed17cdc93c24
products:
  - Marketing Cloud Next
  - Marketing Cloud
---
# Send Transactional Messages with Direct Email Send API

Use Direct Email Send API to send personalized email to one or more recipients in response to activity in your application. Messages are sent immediately through the High Scale Flow (HSF) messaging service. For example, you can use Direct Email Send API for welcome emails, order confirmations, password resets, and account notifications.

The API is available at `https://api.salesforce.com/automation/actions360`.

## Authentication

Use an OAuth Bearer token that has the `sfap_api` scope in your calls to Direct Email Send API. See [Connect to Direct Email Send API](https://developer.salesforce.com/docs/marketing/marketing-cloud-growth/mc-connect-apis/mc-connect-apis-direct-send.md).

## Send Definitions

The API uses send definitions to send messages. A send definition uses the `ListEmail` Salesforce object. It contains references to the email content, the sender identity, tracking options, and metadata for the message. You create a send definition once, then reference its ID in every send request with the `sendDefinitionId` query parameter. Before you send an email, the content that the send definition references must be published in your marketing CMS.

To create a send definition, [use REST API to create a `ListEmail` object](/docs/marketing/marketing-cloud-growth/references/mc-next-email-send-definitions?meta=createSendDefinition), and then deploy the object.

## Endpoints

The API provides three operations, each relative to `https://api.salesforce.com/automation/actions360`.

| Operation                                                                                                                     | Method | Path                          |
| ----------------------------------------------------------------------------------------------------------------------------- | ------ | ----------------------------- |
| [Send to a single recipient](/docs/marketing/marketing-cloud-growth/references/mc-next-email-direct-send?meta=sendEmail)      | POST   | `/messaging/email/v1`         |
| [Send to multiple recipients](/docs/marketing/marketing-cloud-growth/references/mc-next-email-direct-send?meta=sendBulkEmail) | POST   | `/messaging/email/v1/bulk`    |
| [Preview a rendered email](/docs/marketing/marketing-cloud-growth/references/mc-next-email-direct-send?meta=previewEmail)     | POST   | `/messaging/email/v1/preview` |

Every operation requires the `sendDefinitionId` query parameter and an `Authorization: Bearer` header.

## Considerations

Review these considerations before you use Direct Email Send API.

- High Scale Actions and Direct Email Send must be set up in your org. If these features aren’t set up, the API returns a `403 - feature not enabled for tenant` response. Contact your account executive for information about setting up these features.
- The OAuth token must be a JSON Web Token (JWT) with the `sfap_api` scope. You can’t use non-JWT tokens.
- Individual send requests use the `individualId` attribute to identify the recipient. Bulk requests use the `recipients` array.
- The `attributes` object is keyed by the Apex class name defined in your CMS content. The key must match the class name exactly, including case.
- Publish all content referenced in the send definition. A send definition that references draft or missing content produces an empty message body. To confirm that the email renders correctly before you send it, use the preview operation.
- The API enforces rate limits. When a request exceeds the limit, the API returns `429`. If you encounter this error, implement an exponential backoff system and retry.

## See Also

- [Connect to Direct Email Send API](https://developer.salesforce.com/docs/marketing/marketing-cloud-growth/mc-connect-apis/mc-connect-apis-direct-send.md)
- _API Reference_: [Marketing Cloud Send Definitions API](/docs/marketing/marketing-cloud-growth/references/mc-next-email-send-definitions)
- _API Reference_: [Marketing Cloud Direct Send Email API](/docs/marketing/marketing-cloud-growth/references/mc-next-email-direct-send)