Pinpoint: End of Support Oct 2026

[qoricode]

Hi,

The announcement says:

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

However looking at the SDK v4 for .NET (for example), the "SMS & Voice V2" client APIs are still in the Pinpoint namespace and there is no new "End User Messaging" namespace so I'm wondering about practicalities.

Currently using PinpointClient.UpdateXxxTemplate() and PinpointClient.SendMessages() to send messages via any channel. That's all, no use of campaigns, journeys, segments etc..

Does the announcement mean that only email sending need be migrated to the SES client, and e.g. SMS will continue to work via the existing PinpointClient.UpdateSmsTemplate() and PinpointClient.SendMessages() interface? ... which would be convenient as it supports both templating and batching. Or will it be necessary to switch to AmazonPinpointSMSVoiceV2Client.SendMessage() which supports neither, to send messages one by one and use e.g. Handlebars to do templating in advance of sending?

Thanks for your help

David

[dscpinheiro]

Hey David, sorry for the delay in the response but yes once the service reaches end of support, it'll be removed from the .NET SDK and you'll need to migrate. "End User Messaging" is also a bit confusing, but https://www.nuget.org/packages/AWSSDK.PinpointSMSVoiceV2 is the package the documentation is referring to as the recommended alternative.

For the current limitations in the APIs, I'll reach out to the service team internally, but if you have access to https://aws.amazon.com/support/ I recommend leaving feedback there as well (that'll be a good signal that the new approach is missing some functionality you need).