# How to use the transactional response token to debug a transactional API call?

{% hint style="info" %}
This guide is specific to Batch's Mobile Engagement Platform (More on the [difference between Batch's CEP and MEP](https://app.gitbook.com/s/UIK868wiiK9XOVyETGZS/other/faq/what-are-the-differences-between-batch-customer-engagement-platform-and-mobile-engagement-platform)).
{% endhint %}

The [Transactional API](https://doc.batch.com/api/transactional/send) allows you to send action-oriented or time-sensitive push notifications to a specific user ID or to a group of IDs (device token, install ID, or custom user ID).

Once your POST successfully reaches the API endpoint, you should receive an **HTTP 201** confirmation and a unique **Transactional response** **token** representing the transaction.

<figure><img src="https://38998153-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCL8wF0y1T2vLnm3yR2MW%2Fuploads%2Ftes2cWXMYYnX4DbwM3t7%2FtechnicalGuide_tokenexample_12052025.png?alt=media&#x26;token=b2e403c9-6b97-42b7-a9da-0d1048719324" alt=""><figcaption></figcaption></figure>

You can display information related to the transactional push notifications delivery using the **Transactional response token** in the [debug tool](https://doc.batch.com/dashboard/settings/app-settings#transactional-api-debug-tool) (Dashboard settings > Debug). This allows you to check the effective sending time of a transactional push as well as the API call time to monitor potential latencies.

<figure><img src="https://38998153-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCL8wF0y1T2vLnm3yR2MW%2Fuploads%2FANCPvlWsfKRTfYzsazIh%2FtechnicalGuide_debugToken_12052025.png?alt=media&#x26;token=5e9690e8-a76c-45d3-878c-264f818cadd7" alt=""><figcaption></figcaption></figure>

If the POST data does not meet the API requirements, you will receive an [actionable error message](https://doc.batch.com/api/transactional/send#failure).