Dispatch API Migration (2025)

We’ve updated the pulseM Dispatch API (used for integration) from version 1 to version 2, which changes how pulseChecks are counted. A pulseCheck sent by both SMS and email to the same customer now counts as one pulseCheck with two channels, instead of two separate ones.

Example:

Imagine you want to send a pulseCheck to a customer and choose to send it via both SMS and email to increase the chances they see it.

  • In the old system (API Version 1):
    Each channel counted separately. So, if you sent the pulseCheck via SMS and email to the same customer, your reports would show 2 pulseChecks—one for the SMS and one for the email.

  • In the updated system (API Version 2):
    The pulseCheck sent to the same customer across multiple channels is counted as 1 pulseCheck with multiple channels. So, sending via SMS and email counts as 1 pulseCheck that used 2 channels.

What this means for your reports:
You may see fewer total pulseChecks because multiple channels to the same customer are no longer double-counted. However, this gives a more accurate view of unique pulseChecks sent. Your engagement remains strong since the customer still receives the message through both channels—no action is needed on your part.