Submit a Triggered Send Definition Using the Asynchronous API

This page contains information regarding submitting triggered send definitions using the asynchronous API.

Why Submit a Triggered Send Definition Using the Asynchronous API

By using the asynchronous API, you can assign priorities to your API calls or sequence and schedule them for a later date. The asynchronous API also holds calls in queue until it processes them, meaning that the system does not lose your calls in case of an unplanned outage. The asynchronous nature of the calls also prevents unintentional call replays.

How to Submit a Triggered Send Definition Using the Asynchronous API

Use the sample code below as a model to submit your own triggered send definition call to the asynchronous API:

Sample .NET Code

Sample SOAP Envelope

Setting the priority on a triggered sendrequires that more functionality be enabled for your account. Contact your Marketing Cloud representative for more details on this feature and to enable this feature for your account.

How to Retrieve the Status

Use the sample code below as a model to retrieve the status of the triggered send API call:

Sample .NET Code

Sample SOAP Envelope