> **Source:** https://knowledge.leegality.com/document-execution/api/retry-nesl-transaction
> **Site:** Leegality Knowledge Base — https://knowledge.leegality.com
> **About:** Leegality is a document execution platform covering eSigning, stamps, NeSL, workflows, and REST API integration.
> **Navigation:** Every article on this site has a plain-text version at `<article-url>.txt` (this format). To get an index of all articles with their `.txt` links, read: https://knowledge.leegality.com/llms.txt
> **AI Guide:** For instructions on how to navigate this knowledge base as an AI agent, read: https://knowledge.leegality.com/ai-readable.txt

---
# POST /v3.3/nesl/neslRetryRequest — Retry NeSL transaction

Retries a failed NeSL transaction.

**Authentication:** `X-Auth-Token` header required on every request.

## Request URL

```
POST https://app1.leegality.com/api/v3.3/nesl/neslRetryRequest
```

**Environments:**
- Production: `https://app1.leegality.com/api/v3.3/nesl/neslRetryRequest`
- Sandbox: `https://sandbox.leegality.com/api/v3.3/nesl/neslRetryRequest`

---

## Request Body

**Content-Type:** `application/json`

Request body for retrying a NeSL transaction.  At least one of `documentId` or `neslTransactionId` must be provided.

| Field | Type | Required | Description | Example |
|-------|------|----------|-------------|---------|
| `documentId` | string | No | Unique Document ID generated by Leegality for every document in response to a successful create request. | `01KJ7APCJHJZGNRPXWX88MMCRG` |
| `neslTransactionId` | string | No | Unique Transaction ID generated by Leegality for every NeSL document. | `kKoJTQ20Pu` |

### Sample Request

```json
{
  "documentId": "01KJ7APCJHJZGNRPXWX88MMCRG",
  "neslTransactionId": "kKoJTQ20Pu"
}
```

---

## Responses

### 200 — NeSL retry response.

Response wrapper for the Retry NeSL Transaction API.  On a successful retry, `data.retryStatus` is `"SUCCESS"`. On failure, `data` contains the NeSL error details. When input validation fails (missing IDs, document not found), `data` is empty and errors appear in `messages`.

| Field | Type | Required | Description | Example |
|-------|------|----------|-------------|---------|
| `status` | integer | No | API response status.  `1` = success, `0` = failure. Allowed: `0`, `1`. | `0` |
| `messages` | array\<Message\> | No | Array of response messages. Empty array `[]` when the retry request reaches NeSL (regardless of retry outcome). See **Message** below. | — |
| `data` | NeslRetryData | No | NeSL retry result details.  This object is empty when input validation fails (missing IDs, document not found). See **NeslRetryData** below. | — |

#### Message

Message object containing a machine-readable code and a human-readable description. Used for success confirmations, errors, and warnings.

| Field | Type | Required | Description | Example |
|-------|------|----------|-------------|---------|
| `code` | string | No | Response message code. | `simpleWorkFlow.success` |
| `message` | string | No | Human-readable success or error message. | `Invitations sent successfully.` |

#### NeslRetryData

NeSL retry result details.  This object is empty when input validation fails (missing IDs, document not found).

| Field | Type | Required | Description | Example |
|-------|------|----------|-------------|---------|
| `canRetry` | boolean | No | Whether the transaction can be retried.  `true` — retry is allowed, you can call this API again for failed transactions. `false` — retry is not allowed (e.g., due to validation errors that must be fixed first). | `false` |
| `responseCode` | string | No | Response code returned by NeSL.  **Example:** `"ER00J44"` (Invalid First Party Name). | `ER00J44` |
| `responseDescription` | string | No | Human-readable description of the NeSL response code. | `Invalid First Party Name` |
| `retryStatus` | string | No | Outcome of the retry attempt. Allowed: `SUCCESS`, `FAILED`. | `FAILED` |

### Sample Response (200)

```json
{
  "status": 0,
  "messages": [
    {
      "code": "simpleWorkFlow.success",
      "message": "Invitations sent successfully."
    }
  ],
  "data": {
    "canRetry": false,
    "responseCode": "ER00J44",
    "responseDescription": "Invalid First Party Name",
    "retryStatus": "FAILED"
  }
}
```