---
schema_version: "1"
id: 787c5a932598c07eebba357c34b3b2c7109f7f8918444d25a99117b820a91fd6
title: Transactional Messaging API Activities
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/marketing-cloud/guides/mc-apis/transactional-messaging-activities.md
canonical_url: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/transactional-messaging-activities.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 3feeb10ff611ac56e3135594c121b0db909bb6f0c5a1d6660d3dd6d3d2dab3bf
products:
  - Marketing Cloud Engagement APIs and Programmatic Languages
  - Marketing Cloud
---
# Transactional Messaging API Activities

When you send a message using the Transactional Messaging API, it goes through these steps.

1.  Your system sends a transactional message using the Marketing Cloud Engagement Transactional Messaging API.
2.  Information from the API request is applied to the transactional message definition. This step personalizes the message per recipient, assigns recipients to a contact list, and saves request parameters to a data extension, if used.
3.  The Event Notification Service sends the status of the message via a webhook to another system.

![A chart that displays the steps that a transactional message goes through. The flowchart begins by showing a message being sent from REST API. Marketing Cloud Engagement retrieves personalization content applies it to the message. The message is then sent to the subscriber’s inbox, while the response data is sent to the sender’s webhook URL.](https://developer.salesforce.com/docs/media/images/transactional-messaging-activities.png)