**End of support notice:** On October 30, 2026, AWS will end support for Amazon Pinpoint. After October 30, 2026, you will no longer be able to access the Amazon Pinpoint console or Amazon Pinpoint resources (endpoints, segments, campaigns, journeys, and analytics). For more information, see [Amazon Pinpoint end of support](https://docs.aws.amazon.com/console/pinpoint/migration-guide). **Note:** APIs related to SMS, voice, mobile push, OTP, and phone number validate are not impacted by this change and are supported by AWS End User Messaging.

# Send test messages with Amazon Pinpoint
Test messages

With Amazon Pinpoint, you can send *test messages*, which are one-time messages that you send directly to a specific set of recipients. Sending a test message is useful if you want to test the deliverability of a message, or see how a message appears to recipients. You can send a test message by using any channel that Amazon Pinpoint supports.

We charge you for each test message that you send. However, we don't bill you based on your monthly targeted audience (MTA) when you send test messages. For more information, see [Amazon Pinpoint pricing](https://aws.amazon.com/pinpoint/pricing/).

When you use the Amazon Pinpoint console to send a test message, you can send the message to as many as 15 recipients, depending on the type of message. You can't send a test message to a segment—you must send it to individual users. In addition, Amazon Pinpoint delivers a test message immediately. You can't schedule the delivery of a test message. Finally, a test message doesn't generate messaging metrics, such as open, click, or bounce rates. If you want to send a message to a segment, schedule the delivery of a message, or obtain metrics data for a message, you should [create a campaign](campaigns.md) instead of sending a test message.

To send a test message from the Amazon Pinpoint console, use the **Test messaging** page on the console.

**To open the test messaging page**

1. Open the Amazon Pinpoint console at [https://console.aws.amazon.com/pinpoint/](https://console.aws.amazon.com/pinpoint/).

1. On the **All projects** page, choose the project that you want to send a test message for.

1. In the navigation pane, choose **Test messaging**.

# Sending a test email message
Sending an email message

To send a test email message, you must use a project that has the email channel enabled. To learn how to create a new project and enable the email channel for it, see [Setting up the Amazon Pinpoint email channel](channels-email-setup.md). To learn how to enable the email channel for an existing project, see [Managing the Amazon Pinpoint email channel](channels-email-manage.md).

**To send a test email message**

1. Open the Amazon Pinpoint console at [https://console.aws.amazon.com/pinpoint/](https://console.aws.amazon.com/pinpoint/).

1. On the **All projects** page, choose the project that you want to send a test message for.

1. In the navigation pane, choose **Test messaging**.

1. On the **Test messaging** page, under **Channel**, choose **Email**.

1. For **Destination type**, choose one of the following destinations for your message:
   + **Email addresses** – Each destination is a recipient's email address.
   + **Endpoint IDs** – Each destination is a unique ID that's assigned to an endpoint for the project.

1. Depending on your selection for **Destination type**, enter one or more **Endpoint IDs** or **Email addresses**. You can enter up to 15 values. Use commas to separate multiple values.

1. For **Message content**, choose whether you want to **Create a new message** or **Use an existing template**. 
**Note**  
The maximum email message size for **Create a new message** is 200 KB. You can use email templates to send larger email messages.

   If you choose to use an existing template, choose the template from the **Template** list. After you choose a template, Amazon Pinpoint displays a preview of the active version of the template. The active version is typically the version of a template that's been reviewed and approved for use, depending on your workflow.

   If you choose to create a new message, specify a subject in the **Subject** field, and a message body in the **Message** field.
**Tip**  
You can enter the message body by using either HTML or Design view. In the HTML view, you can manually enter HTML content for the message body, including formatting, links, and other features that you want to include in the message. In the Design view, you can use a rich text editor to enter the content of the message body. You can use the formatting toolbar to apply formatting and add links and other features to the message body. To switch views, choose **HTML** or **Design** from the view selector above the message editor.

   In the field below the message editor, optionally enter the content that you want to display in the body of messages that are sent to recipients whose email applications don't display HTML content.

1. 
**Note**  
You must set up an email orchestration sending role before you can use email headers. For more information, see [Creating an email orchestration sending role in Amazon Pinpoint](channels-email-orchestration-sending-role.md).

   Under **Headers**, choose **Add new headers**, to add up to 15 headers for the email message. For a list of supported headers, see [Amazon SES header fields](https://docs.aws.amazon.com/ses/latest/dg/header-fields.html) in the [Amazon Simple Email Service Developer Guide](https://docs.aws.amazon.com//ses/latest/dg/Welcome.html).
   + For **Name**, enter the name of the header.
   + For **Value**, enter the value of the header.

   (Optional) To add a One-click unsubscribe link to a promotional email, add the following two headers:

   1. Create a header with `List-Unsubscribe` for **Name** and set **Value** to your unsubscribe link. The link must support HTTP POST requests to process the recipients unsubscribe request.

   1. Create a header with `List-Unsubscribe-Post` for **Name** and set **Value** to `List-Unsubscribe=One-Click`.

1. When you finish, choose **Send message**.

# Sending a test push notification
Sending a push notification

To send a test push notification, you must use a project that has one or more push notification channels enabled. To learn how to create a new project and enable a push notification channel for it, see [Creating an application and enabling push channels](https://docs.aws.amazon.com/push-notifications/latest/userguide/procedure-enable-push.html) in the *AWS End User Messaging Push User Guide*.

After you enable one or more push notification channels for a project, you can send a test push notification through any of those channels.

**To send a test push notification**

1. Open the Amazon Pinpoint console at [https://console.aws.amazon.com/pinpoint/](https://console.aws.amazon.com/pinpoint/).

1. On the **All projects** page, choose the project that you want to send a test message for.

1. In the navigation pane, choose **Test messaging**.

1. On the **Test messaging** page, under **Channel**, choose **Push notifications**.

1. For **Destination type**, choose one of the following destinations for your message:
   + **Endpoint IDs** – Each destination is a unique ID that's assigned to an endpoint for the project.
   + **Device tokens** – Each destination is a token that's assigned to the instance of the app that you're messaging. For example, this value can be a device token that's assigned by the Apple Push Notification service (APNs) or a registration token that's assigned by Firebase Cloud Messaging (FCM).

1. Depending on your selection for **Destination type**, enter one or more **Endpoint IDs** or **Device tokens**. You can enter up to 15 values. Use commas to separate multiple values.

   If you use device tokens as the destination type, you should only specify tokens that are associated with a single push notification service. Amazon Pinpoint can send the message through only one push notification service at a time.

   If you use endpoint IDs as the destination type, this restriction doesn't apply. You can specify endpoints that use any push notification service.

1. For **Push notification service**, specify the push notification service that you want to send the message through. If you use endpoint IDs as the destination type, Amazon Pinpoint detects the service automatically.

1. For **Notification type**, specify the type of test message that you want to send:
   + **Standard message** – A push notification that has a title, a message body, and other content and settings. Recipients are alerted by their mobile devices when they receive the message.
   + **Raw message** – A push notification that specifies all of a notification's content and settings as a JSON object. This type of notification can be useful for cases such as sending custom data to an app for processing by that app, instead of the push notification service. If you choose this option, the message editor displays an outline of the code to use for the message. In the message editor, enter the settings that you want to use for each push notification service. Include any optional settings (such as images, sounds, and actions) that you want to specify. For more information, see the documentation for the push notification services that you use. When you finish entering all the raw message content, skip to step 12.

1. Under **Message**, for **Message content**, choose whether you want to **Create a new message** or **Use an existing template**. 

   If you choose to use an existing template, choose the template from the **Template** list. After you choose a template from the list, Amazon Pinpoint displays a preview of the active version of the template. (The active version is typically the version of a template that's been reviewed and approved for use, depending on your workflow.) When you finish choosing a template, skip to step 12.

   If you choose to create a new message, specify a **Title** and **Body** for the message.

1. For **Action**, select the action that you want to occur if the recipient taps the notification:
   + **Open app** – Your app launches, or it becomes the foreground app if it was sent to the background.
   + **Go to URL** – The default mobile browser on the recipient's device launches and opens a webpage at the URL that you specify. For example, this action is useful for sending users to a blog post.
   + **Open a deep link** – Your app opens and displays a designated user interface in the app. Deep linking is an iOS and Android feature. For example, this action is useful for directing users to special promotions for in-app purchases.

1. (Optional) In the **Media URLs** section, provide URLs that point to media files that you want to display in the message. The URLs must be publicly accessible so that push notification services can retrieve the files.

1. When you finish, choose **Send message**.

# Sending a test SMS message
Sending an SMS message

To send a test SMS message, you must use a project that has the SMS channel enabled. To learn how to create a new project and enable the SMS channel for it, see [Setting up the Amazon Pinpoint SMS channel](channels-sms-setup.md). To learn how to enable the SMS channel for an existing project, see [Managing the Amazon Pinpoint SMS channel](channels-sms-manage.md).

**To send a test SMS message**

1. Open the Amazon Pinpoint console at [https://console.aws.amazon.com/pinpoint/](https://console.aws.amazon.com/pinpoint/).

1. On the **All projects** page, choose the project that you want to send a test message for.

1. In the navigation pane, choose **Test messaging**.

1. On the **Test messaging** page, under **Channel**, choose **SMS**.

1. For **Destination type**, choose one of the following destinations for your message:
   + **Phone numbers** – Each destination is a recipient's phone number.
   + **Endpoint IDs** – Each destination is a unique ID that's assigned to an endpoint for the project.

1. Depending on your selection for **Destination type**, enter one or more **Endpoint IDs** or **Phone numbers**. You can enter up to 15 values. Use commas to separate multiple values.

   If you use phone numbers as the destination type, specify each number in E.164 format. E.164 is a standard for the phone number structure that's used for international telecommunication. Phone numbers that follow this format typically have up to 15 digits, and they are prefixed with the plus character (\$1) and the country code. For example, a US phone number in E.164 format appears as \$112065550100.

1. (Optional) For the **Origination phone number**, select a phone number to send the message from. This list contains all of the dedicated phone numbers that are associated with your account. If your account contains multiple dedicated phone numbers, and you don't choose an origination number, Amazon Pinpoint looks for a short code in your account; if it finds one, it uses that short code to send the message. If a short code isn't found in your account, then it looks for a 10DLC number (US recipients only), and then a toll-free number (US recipients only), and then a long code.

1. For **Message type**, choose one of the following:
   + **Promotional** – Noncritical messages, such as marketing messages. If you choose this option, Amazon Pinpoint optimizes the message delivery to incur the lowest cost.
   + **Transactional** – Critical messages that support customer transactions, such as one-time passwords for multi-factor authentication. If you choose this option, Amazon Pinpoint optimizes the message delivery to achieve the highest reliability.
**Note**  
This message-level setting overrides the default message type that you chose on the **Settings** page for the project.

1. Under **Message**, for **Message content**, choose whether you want to **Create a new message** or **Use an existing template**. 

   If you choose to use an existing template, choose the template from the **Template** list. After you choose a template from the list, Amazon Pinpoint displays a preview of the active version of the template. (The active version is typically the version of a template that's been reviewed and approved for use, depending on your workflow.) When you finish choosing a template, skip to step 10.

   If you choose to create a new message, specify the content of the message in the **Message** field.

1. (Optional) For **Sender ID**, enter a custom ID that contains up to 11 alphanumeric characters, including at least one letter, and no spaces. The sender ID is displayed as the message sender on the recipient's device. For example, you can use your business brand to make the message source easier to recognize.

   Support for sender IDs varies by country and region. For more information, see [Supported countries and regions (SMS channel)](https://docs.aws.amazon.com//sms-voice/latest/userguide/phone-numbers-sms-by-country.html) in the *AWS End User Messaging SMS User Guide*.

   This message-level sender ID overrides your default sender ID, which you chose on the **Settings** page for the project.

1. When you finish, choose **Send message**.