> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/developer/technical-guides/how-to-guides/backend/how-to-use-the-transactional-response-token-to-debug-a-transactional-api-call.md).

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

Here is what you need to do when you want to check the effective sending time of a transactional push compared to the API call time.

{% hint style="info" %}
This guide is specific to Batch's Mobile Engagement Platform (More on the [difference between Batch's CEP and MEP](/getting-started/other/faq/what-are-the-differences-between-batch-customer-engagement-platform-and-mobile-engagement-platform.md)).
{% 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&amp;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&amp;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).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.batch.com/developer/technical-guides/how-to-guides/backend/how-to-use-the-transactional-response-token-to-debug-a-transactional-api-call.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.