> 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?
{% 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.
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.
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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
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=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.