---
schema_version: "1"
id: cc9cf6dfeee4875c4895e3f88334d6a11a6a6b4217abdfe3b7519a0de122e685
title: Single-Send Journeys
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/marketing-cloud/guides/mc-apis/single-send-journeys.md
canonical_url: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/single-send-journeys.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: f67420fe17a3ac7dc3d7046b23aa7d3639f6d4f8cbf6b17a7edec2f9cf9068aa
products:
  - Marketing Cloud Engagement APIs and Programmatic Languages
  - Marketing Cloud
---
# 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](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/getting-started-spec.md), 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.