---
schema_version: "1"
id: 7da9014549b8da7309a44b9099985009afa533022464449b55c103657321bb34
title: Create a Triggered Send Definition
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/marketing-cloud/guides/mc-apis/creating_a_triggered_send_definition.md
canonical_url: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/creating_a_triggered_send_definition.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 5ce2edab5c0949b6dc2b19693dd23013b128acbc29e76c1200495bf299f4a31f
products:
  - Marketing Cloud Engagement APIs and Programmatic Languages
  - Marketing Cloud
---
# Create a Triggered Send Definition

**note:** This documentation applies only to triggered sends that are managed in Email Studio. To use the transactional messaging REST API, review [Transactional Messaging API](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/transactional-messaging-api.md).

Create a triggered send definition that an external application can reference to send a message to subscribers. For example, send an email when subscribers submit a sign-up form.

You can create up to 500 email send definitions in a 7-day period per business unit. This limit doesn’t apply to the Journey Builder email activity triggered send definition.

## Sample SOAP Envelope

When you update a triggered send definition via the SOAP API with the Email object, you must set the EmailSubject property on the triggered send definition. If you don't pass the new subject to the triggered send definition, it retains the old subject for that definition.

```xml
<s:Envelope
  xmlns:s="http://www.w3.org/2003/05/soap-envelope"
  xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing"
  xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
  <s:Header>
    <a:Action s:mustUnderstand="1">Create</a:Action>
    <a:To s:mustUnderstand="1">https://YOUR_SUBDOMAIN.soap.marketingcloudapis.com/Service.asmx</a:To>
    <fueloauth xmlns="http://exacttarget.com">YOUR_ACCESS_TOKEN</fueloauth>
  </s:Header>
  <s:Body
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <CreateRequest xmlns="http://exacttarget.com/wsdl/partnerAPI">
      <Options></Options>
      <Objects xsi:type="TriggeredSendDefinition">
        <PartnerKey xsi:nil="true"></PartnerKey>
        <ObjectID xsi:nil="true"></ObjectID>
        <CustomerKey>TSD</CustomerKey>
        <Name>TSD</Name>
        <SendClassification>
          <PartnerKey xsi:nil="true"></PartnerKey>
          <CustomerKey>12345</CustomerKey>
          <ObjectID xsi:nil="true"></ObjectID>
        </SendClassification>
        <Email>
          <PartnerKey xsi:nil="true"></PartnerKey>
          <ObjectID xsi:nil="true"></ObjectID>
          <ID>123456</ID>
        </Email>
        <SendSourceDataExtension>
          <CustomerKey>EmptyTriggeredSendDE</CustomerKey>
        </SendSourceDataExtension>
      </Objects>
    </CreateRequest>
  </s:Body>
</s:Envelope>
```

## Related Items

- _Salesforce Help_: [Triggered Emails](https://help.salesforce.com/articleView?id=mktg.mc_es_triggered_emails.htm)