Get Started with Transactional Messaging API

Ensure that your client ID and secret are stored securely. Never expose this information on the client side via JavaScript or store it in a mobile application.

Tip: To save the attributes sent in the API request, create a triggered send data extension in Email Studio.

Send a Transactional Email Message

  1. Get an access token to generate API requests: Server-to-server integrations and web and public app integrations. To authenticate all your API requests, use an access token. You can reuse the access token for multiple requests before it expires.
  2. Set up an email send definition via the API. The send definition contains the message template and delivery configuration. You must reference a send definition with each message API request.
  3. Send a transactional email. Send your email to one or more recipients when triggered by an API.
  4. Create an optional subscription. A subscription uses a webhook to send you analytics in real time about whether emails are sent, not sent, or bounced.

Send a Transactional SMS Message

  1. Get an access token to generate API requests: Server-to-server integrations and web and public app integrations. To authenticate all your API requests, use an access token. You can reuse the access token for multiple requests before it expires.
  2. Set up a transactional SMS definition via the API. The send definition contains the message template and delivery configuration. We recommend that you set up a definition for each messaging use case, such as one for two-factor authentication and one for order confirmations. You must reference a send definition with each outbound SMS send API request.
  3. Send a transactional SMS. Send your SMS to one or more recipients when triggered by the API.
  4. Create an optional subscription. A subscription uses a webhook to send you analytics in real time about whether SMS messages are sent, not sent, or bounced.