# Batch Send - Retry

Retries all failed messages that belongs to a batch. All messages that are retried will retain their original message ID.

The batch retry endpoint will only return a `HTTP 201` response if&#x20;

1. the batch `status` is `messages_enqueued` or `messages_enqueuing_failed`.

Note that batch retry will fail if any of the messages that belongs to the batch has `latestStatus` of `created`. In this case, batch `status` will be set to `messages_enqueuing_failed`.

The Batch Send - Retry feature behaves the same way as the [Batch Send](/endpoints-for-api-users/batch-send.md)[ ](/endpoints-for-api-users/single-send.md)feature.

Note that in your retry endpoint, the `batchId`  remains the same, and is generated from the original request in your [Batch Send](/endpoints-for-api-users/batch-send.md).

{% code overflow="wrap" %}

```javascript
POST /campaigns/:campaignId/batch/:batchId/retry
```

{% endcode %}

{% code title="Response Body" %}

```json
// This endpoint has no response body
// A HTTP 201 response will be returned if the batch retry is attempted.
```

{% endcode %}


---

# Agent Instructions: 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:

```
GET https://postman-v2.guides.gov.sg/endpoints-for-api-users/batch-send-retry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
