Single-Send Journeys

There are two types of Journey Builder sends:

Multi-step journeys
Single-send journeys

Most use cases for interacting with journeys via API involve multi-step journeys. Multi-step journeys enable you to create and manage customer journeys through a series of interactions with your brand. These journeys can include multiple channels and customized journey paths based on customer interactions or attributes. Multi-step journeys can also have different activities and versions. The Journey Builder developer documentation is based on multi-step journeys.

You can employ single-send journeys for simple, single-use journeys that marketers create in Journey Builder. However, you can interact with single-send journeys via API, if required, by modifying the journey specification. Goals, versions, and recurring scheduling aren’t supported for single-send journeys. Email, SMS, and push notifications are the only activities available for single-send journeys.

Specification for Single-Send Journeys

To set up a single-send journey via API, follow the journey specification, with these key modifications:

In the journey object, use Quicksend for the definitionType parameter.
In the journey object, for the channel parameter, use one of the following values: email for email, push for push notifications, or sms for SMS messages.
In the activity object, for the type parameter in the activities list, use one of the following values: emailv2 for email, pushnotificationactivity for push notifications, or smssync for SMS messages. You can define only one activity.
In the trigger portion of the event object, use EmailAudience as the type parameter for email messages and SMS messages, and use ContactAudience as the type parameter for push notifications. EmailAudience is the same as the data extension entry source in Journey Builder.
Don’t include goals, versioning, or a recurrent schedule.