> For the complete documentation index, see [llms.txt](https://postman-v2.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postman-v2.guides.gov.sg/faq/postman-v2-sms-api-faq/delivery-report.md).

# Delivery Report

1. **Will specific error codes be shown for SMS failures?**

   * Yes, it will be in the delivery report that can be downloaded for each campaign. This will come in the form of a CSV file all messages ever sent for the batch or campaign. You should filter for the desired month within the CSV file itself.

2. **How long will campaign logs be retained for?**

   * They are stored indefinitely.

3. **If a message is sent out in a batch and has an error, will there be individual error logs for the messages that failed to send?**

   * Yes, individual error logs will be available.

     The messages in the batch will be sent out except for those that have failed.

4. **Are there any differences between Postman v1 and Postman v2**

   * The original Postman (now named “Postman v1”) will only serve the function of sending emails. Public healthcare institutions can still use Postman v1 to send SMSes. You may access Postman v1 via <https://postman.gov.sg/>
   * The new Postman (”Postman v2”) will give users the functionalities of sending SMSes to MOP using the `gov.sg` sender ID, or to internal staff using their own registered sender IDs. All other government agencies should use Postman v2 for SMS sending through `gov.sg` or to internal staff. You may access Postman v2 test site via [https://test.postman.gov.sg/](https://postman.gov.sg/)

5. **If messages fail to be delivered, will they be charged?**
   * Yes.


---

# 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://postman-v2.guides.gov.sg/faq/postman-v2-sms-api-faq/delivery-report.md?ask=<question>&goal=<endgoal>
```

`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.