> **Source:** https://knowledge.leegality.com/document-execution/api/error-reference
> **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

---
# Error Reference

Error code reference for the Document Execution APIs.

### SSL/TLS Connection Errors

SSL/TLS Connection Errors occur when a secure HTTPS connection cannot be established between the client application and the Leegality server. As a result, the API request fails before it reaches the application layer.

**Common Root Causes:**

- **TLS Version Mismatch:** Client is using an older TLS version (e.g., TLS 1.0 or TLS 1.1) while the server supports only TLS 1.2 or above.
- **Untrusted or Missing Root/Intermediate Certificates:** The client system does not trust the certificate chain presented by the server.
- **SSL Certificate Validation Failure:** Hostname mismatch, expired certificate, or invalid certificate chain.
- **Firewall or Proxy Interference:** Corporate firewall or proxy is intercepting SSL traffic and preventing successful handshake.
- **SSL Handshake Failure:** Cipher suite mismatch between client and server, or unsupported encryption algorithms.
- **Network Connectivity Issues:** Intermittent network failures causing connection termination during SSL negotiation.
- **Incorrect Trust Store Configuration:** Required root/intermediate certificates are not imported into the application's trust store (Java Keystore, Windows Certificate Store, etc.).
- **Mutual TLS (mTLS) Configuration Issues:** If applicable, client certificate is missing, expired, or incorrectly configured.

<table>
<thead>
<tr><th>Code</th><th>Message</th><th>Description</th><th>Solution</th></tr>
</thead>
<tbody>
<tr>
<td><em>(TLS handshake failure)</em></td>
<td><ul><li><code>SSLHandshakeException</code></li><li><code>PKIX path building failed</code></li><li><code>Certificate path validation failed</code></li><li><code>Received fatal alert: handshake_failure</code></li><li><code>Unable to find valid certification path to requested target</code></li><li><code>javax.net.ssl.SSLException</code></li><li><code>A timeout error occurred whilst performing an SSL socket operation</code></li></ul></td>
<td>The client cannot establish a secure TLS connection with the Leegality server.</td>
<td><ol><li>Verify the endpoint URL is HTTPS.</li><li>Confirm the client supports TLS 1.2 or higher.</li><li>Check whether the SSL certificate is valid and trusted.</li><li>Verify firewall/proxy restrictions.</li><li>Review application logs for SSL handshake exceptions.</li><li>Test connectivity using tools such as OpenSSL, Postman, or Curl.</li><li>Compare successful and failed requests.</li><li>Check whether the issue occurs for all API calls or only specific endpoints.</li></ol></td>
</tr>
</tbody>
</table>

### Authentication Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| null | Access Denied | The `X-Auth-Token` header is missing from the request | Add the `X-Auth-Token` header with a valid authentication token |
| *(empty)* | *(HTTP 401/403)* | The provided authentication token is invalid or expired | Obtain a new valid authentication token from the dashboard |

### Required Field Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| null | Property profileId cannot be null | The `profileId` field is missing or set to null | Provide a valid workflow profile ID in the `profileId` field |
| null | Property file cannot be null | The `file` object is missing from the request | Include a `file` object with either `base64` content or `fields` array |
| workflow.api.fields.or.file.required | Either file base64 or fields required for file. | The `file.fields` array is empty, OR the `profileId` is invalid/non-existent | Provide either `file.file` with document content OR `file.fields` with form field values. Also verify the `profileId` exists |
| simpleWorkFlow.no.payload.invitee | Either send Invitees data or configure at least one Invitees in dashboard | The `invitees` array is empty and no invitees are configured in dashboard | Provide at least one invitee in the `invitees` array with name and email/phone |

### Invitee Validation Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| null | Invitee(N) name is required. | The invitee at index N has an empty or missing name | Provide a non-empty `name` for each invitee |
| null | Invitee(N) email or phone is required. | The invitee at index N has neither email nor phone | Provide at least one of `email` or `phone` for each invitee |
| null | Invitee(N) email is invalid. | The email format for invitee at index N is invalid | Provide a valid email address (e.g., `user@domain.com`) |
| signer.reviewer.name.invalid[N] | Signer/Reviewer name is invalid for invitee N. | The invitee name contains invalid special characters (`<`, `>`, `'`, `&`, etc.) or Unicode | Use only alphanumeric characters, spaces, and basic punctuation (`.`, `-`, `,`) in names |
| invitee.org.name.invalid[N] | Organisation name, under company seal, is invalid for Invitee N. | The `organizationName` contains invalid characters (HTML tags, `<`, `>`, etc.) | Use only alphanumeric characters and basic punctuation in organization name |
| invalid.group.name[N] | Invalid input in Group Name. | The `groupName` contains invalid special characters | Use only alphanumeric characters and allowed special chars: `| - : () , _. [] & / # + @` |

### File & Fields Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| null | Property file cannot be null | The `file` object is completely missing | Include a `file` object in your request |
| workflow.api.fields.or.file.required | Either file base64 or fields required for file. | Neither `file.file` nor `file.fields` is provided, or `fields` is an empty array | Provide `file.file` with base64-encoded document content, OR provide `file.fields` array with field values matching the workflow template |

### IRN Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| irn.length.invalid | IRN can not be greater than 255 characters. | The Internal Reference Number exceeds 255 characters | Shorten the IRN to 255 characters or less |

### Stamp Configuration Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| null | Stamp Series required for this Workflow Profile | Stamp is enabled in workflow but `stampSeries` or `multipleStampSeries` is missing/empty/null | Provide a valid `stampSeries` or `multipleStampSeries` array when stamp is enabled in the workflow |
| invalid.stamp.series.value | Invalid input in stamp series. Allowed input includes numeric characters only. | The `stampSeries` contains non-numeric characters | Use only numeric characters (0-9) for stamp series. Example: `"03"` not `"TEST-03"` |
| no.active.series.or.no.stamp.found | No active series found or sufficient active stamps not found in the series. | The stamp series doesn't exist, has no available stamps, or the format doesn't match exactly | Verify the series exists in dashboard, check stamp availability, match format exactly (e.g., `"03"` not `"3"` or `"003"`) |
| workflow.stamp.series.mismatch | Stamp Series Number [X] mismatch with configured workflow. | The API-provided stamp series doesn't match the pre-configured series in dashboard | Use the exact stamp series configured in the workflow dashboard |
| multiple.stamp.states.used | Please use stamps of same state only. | The `multipleStampSeries` array contains stamps from different states | Ensure all stamps in `multipleStampSeries` are from the same state |
| stamp.quantity.less.than.1 | For multiple series minimum quantity per series is 1. | The `seriesQuantity` is 0, empty, or missing | Provide `seriesQuantity` with a value of at least `"1"` for each entry |
| invalid.stamp.series.group | Invalid input in stamp group. Allowed input includes alphanumeric characters only. | The `seriesGroup` contains special characters | Use only alphanumeric characters (A-Z, a-z, 0-9) for `seriesGroup` |
| workflow.excel.stamp.amount.invalid | Invalid Stamp Amount/Quantity. | The `stampValue` contains non-numeric characters | Provide a numeric string for `stampValue`. Example: `"100"` not `"abc"` |
| stamp.value.exceeds.maximum.allowed.group.limit | Stamp value exceeds maximum allowed series group limit. | The `stampValue` exceeds the maximum allowed for the series group | Reduce the `stampValue` to within the allowed limit |
| invalid.revenue.stamp.series | Invalid input in revenue stamp. Allowed input includes numeric characters only. | The `revenueStampSeries` contains non-numeric characters | Use only numeric characters for `revenueStampSeries` |
| stamp.group.does.not.exist | Stamp group does not exist. | The `seriesGroup` value doesn't match any existing stamp group | Use a valid stamp group code that exists in your account |
| no.stamp.combinations.found | Insufficient stamps in the stamp group to create desired stamp value. | The stamp group doesn't have enough stamps to create the requested value | Reduce the `stampValue` or ensure the stamp group has sufficient stamps |
| selected.group.max.value.exceeded | Maximum allowed value for the selected group is Rs [X]... | The `stampValue` exceeds the maximum configured for the stamp group | Reduce the `stampValue` to be within the group's configured maximum |
| null | Stamp Group is required for this Profile. | `seriesGroup` is missing when stamp group feature is enabled | Provide a valid `seriesGroup` value |
| null | Stamp Amount is required. | `stampValue` is missing or zero when stamp group feature is enabled | Provide a valid non-zero `stampValue` |

### Face Match Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| workflow.face.match.invalid.image | The reference image for face match is either empty or invalid (max size - 4.5MB, formats - jpg, jpeg or png). | The `faceMatchImage` is empty, missing, or exceeds size/format limits | Provide a valid base64-encoded image (jpg/jpeg/png, max 4.5MB) |
| invitee.invalid.face.match.image | Face Match Image type is invalid. | The `faceMatchImage` contains invalid base64 data or includes a data URI prefix | Remove any data URI prefix (e.g., `data:image/png;base64,`) and provide only the raw base64 string |

### GPS Configuration Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| typeMismatch | Property allowedLatitude is type-mismatched | The GPS coordinates are not in the correct format (non-numeric) | Provide coordinates as string decimal values. Example: `"29.982643"` |
| location.restriction.true.allowed.longitude.required | allowedLongitude configured mandatory when applyLocationRestriction=true, value is required. | GPS location restriction is enabled but longitude is empty | Provide both `allowedLatitude` and `allowedLongitude` when `applyLocationRestriction` is true |
| location.restriction.true.allowed.latitude.required | allowedLatitude configured mandatory when applyLocationRestriction=true, value is required. | GPS location restriction is enabled but latitude is empty | Provide both `allowedLatitude` and `allowedLongitude` when `applyLocationRestriction` is true |
| invalid.gps.accuracy.permissableRadius | Invalid Permissible Radius. Enter any number from 0 to 9999999 | The `permissibleRadius` is negative or outside the valid range | Provide a value between 0 and 9999999 |
| invalid.gps.accuracy.deviation | Please enter a valid value for Default Allowed Accuracy Deviation Acceptance Condition (Range : 0-99999) | The `accuracyThreshold` is negative or outside the valid range | Provide a value between 0 and 99999 |

### Group Invitee Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| null | Group Id: [ID], Group name is required. | A group invitee is missing the `groupName` field | Provide `groupName` for all invitees with a `groupId` |
| null | Group Name: [name], Completion Threshold is required. | The `completionThreshold` is missing, empty, or zero for a group | Provide a `completionThreshold` value of at least 1 |
| null | GroupName: [name], Completion Threshold value cannot be greater than invitees in group. | The `completionThreshold` exceeds the number of invitees in the group | Set `completionThreshold` to be less than or equal to the number of invitees in the group |
| group.invitees.workflow.incorrect.payload | Group ID [ID] cannot have more than 0 Invitees. | The `groupId` doesn't match the workflow-configured group | Use the exact `groupId` configured in the workflow dashboard |

### 2FA Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| null | Invitee(N) Two-Factor Authentication enabled hence Email and Phone No. can not be empty. | 2FA is enabled but the invitee is missing email or phone | Provide BOTH `email` AND `phone` for all invitees when 2FA is enabled |

### CC Recipients Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| null | CCInvitee(N) email is invalid. Either send CC Invitees data or configure in dashboard. | The CC recipient email format is invalid OR CC configuration mismatch | Provide a valid email address for CC recipients and ensure CC invitees are configured in dashboard |

### Signing-Time Errors

These errors occur during the signing process, not at document creation. The API accepts these configurations but signing fails.

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| *(signing error)* | You are outside the permissible area. | The signer's GPS location is outside the allowed radius | Verify coordinates are correct, increase `permissibleRadius`. Do not use `permissibleRadius: 0` |
| *(signing error)* | Your GPS location accuracy is low. | The signer's device GPS accuracy doesn't meet the threshold | Increase `accuracyThreshold` to a reasonable value (e.g., 100-1000). Do not use `accuracyThreshold: 0` |

### GPS Config Ignored (Feature Not Enabled)

> **Warning — warnings**
>
> These are warnings returned in a successful response (status: 1). The request succeeds but values are ignored.

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| workflow.captureLocation.off.allowed.latitude.ignored | Invitee(N) captureLocation is not on. allowedLatitude value ignored. | GPS is not enabled in workflow but coordinates were sent | Enable GPS in workflow dashboard, or remove `gpsConfig` from request |
| workflow.captureLocation.off.allowed.longitude.ignored | Invitee(N) captureLocation is not on. allowedLongitude value ignored. | GPS is not enabled in workflow but coordinates were sent | Enable GPS in workflow dashboard, or remove `gpsConfig` from request |
| workflow.captureLocation.off.permissable.radius.ignored | Invitee(N) captureLocation is not on. permissableRadius value ignored. | GPS is not enabled in workflow but radius was sent | Enable GPS in workflow dashboard, or remove `gpsConfig` from request |

### GPS Config Ignored (Toggle OFF)

> **Warning — warnings**
>
> These are warnings returned in a successful response (status: 1). The request succeeds but values are ignored.

When "Allow sender to make changes while running" toggle is OFF in dashboard:

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| workflow.allowGpsConfigChange.off.allowed.latitude.ignored | Invitee(N) allowGpsConfigChange is not on. allowedLatitude value ignored. | API latitude is ignored; dashboard value used instead | Turn ON "Allow sender to make changes" toggle in workflow |
| workflow.allowGpsConfigChange.off.allowed.longitude.ignored | Invitee(N) allowGpsConfigChange is not on. allowedLongitude value ignored. | API longitude is ignored; dashboard value used instead | Turn ON "Allow sender to make changes" toggle in workflow |
| workflow.allowGpsConfigChange.off.permissable.radius.ignored | Invitee(N) allowGpsConfigChange is not on. permissableRadius value ignored. | API radius is ignored; dashboard value used instead | Turn ON "Allow sender to make changes" toggle in workflow |
| workflow.allowGpsConfigChange.off.accuracy.deviation.ignored | Invitee(N) allowGpsConfigChange is not on. accuracyThreshold value ignored. | API accuracy threshold is ignored; dashboard value used instead | Turn ON "Allow sender to make changes" toggle in workflow |
| workflow.allowGpsConfigChange.off.location.restriction.ignored | Invitee(N) allowGpsConfigChange is not on. applyLocationRestriction value ignored. | API location restriction flag is ignored | Turn ON "Allow sender to make changes" toggle in workflow |
| workflow.allowGpsConfigChange.off.accuracy.restriction.ignored | Invitee(N) allowGpsConfigChange is not on. applyLocationAccuracy value ignored. | API accuracy restriction flag is ignored | Turn ON "Allow sender to make changes" toggle in workflow |

### Stamp Group Ignored (Dashboard Pre-defined)

> **Warning — warnings**
>
> These are warnings returned in a successful response (status: 1). The request succeeds but values are ignored.

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| workflow.stamp.warning | Warning: Stamp series already assigned to profile, given value for stamp series ignored. | seriesGroup is pre-defined in dashboard; API value is ignored | Use the dashboard-configured seriesGroup value, or remove seriesGroup from request |

### Aadhaar Config Ignored (Verification Disabled)

> **Warning — warnings**
>
> These are warnings returned in a successful response (status: 1). The request succeeds but values are ignored.

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| invitee.aadhaar.config.verify.certificate.off.property.ignored | Invitee(N) verify certificate details is not on. [property] value ignored. | Aadhaar verification master toggle not enabled | Enable Aadhaar verification in workflow dashboard |
| invitee.aadhaar.config.verify.off.name.ignored | Invitee(N) verifyNameOn is not on. verifyName value ignored. | Name verification toggle disabled | Enable "Verify Name" toggle on dashboard |
| invitee.aadhaar.config.verify.off.smartname.ignored | Invitee(N) verifySmartNameOn is not on. verifySmartName value ignored. | Smart name verification toggle disabled | Enable "Verify Smart Name" toggle on dashboard |
| invitee.aadhaar.config.verify.off.yob.ignored | Invitee(N) verifyYobOn is not on. verifyYob value ignored. | Year of birth verification toggle disabled | Enable "Verify YOB" toggle on dashboard |
| invitee.aadhaar.config.verify.off.gender.ignored | Invitee(N) verifyGenderOn is not on. verifyGender value ignored. | Gender verification toggle disabled | Enable "Verify Gender" toggle on dashboard |
| invitee.aadhaar.config.verify.off.title.ignored | Invitee(N) verifyTitleOn is not on. verifyTitle value ignored. | Title verification toggle disabled | Enable "Verify Title" toggle on dashboard |
| invitee.aadhaar.config.verify.off.pincode.ignored | Invitee(N) verifyPincodeOn is not on. verifyPincode value ignored. | Pincode verification toggle disabled | Enable "Verify Pincode" toggle on dashboard |
| invitee.aadhaar.config.verify.off.state.ignored | Invitee(N) verifyStateOn is not on. verifyState value ignored. | State verification toggle disabled | Enable "Verify State" toggle on dashboard |

### Aadhaar Config Validation Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| typeMismatch[N] | Property N is type-mismatched | Aadhaar field has wrong type (e.g., string instead of boolean, or invalid enum value) | Check field types: verifyName/verifySmartName are booleans; verifyYob/verifyGender/verifyState/verifyPincode are strings |
| certificate.pin.code.invalid[N] | Certificate pin code is invalid for invitee N. | Invalid pincode format in verifyPincode | Use valid 6-digit numeric pincode string (e.g., `"110001"`) |
| certificate.title.invalid[N] | Certificate title is invalid for invitee N. | Invalid verifyTitle format | Use last 4 digits of Aadhaar number (e.g., `"3870"`), NOT titles like "Mr"/"Shri" |
| null | Invitee(N) configured mandatory for Aadhaar [field] verification, value is required. | Toggle is enabled on dashboard but API didn't send value | Provide value for enabled verification fields |

### NeSL Required Data Errors

These errors occur when required NeSL data is missing or incomplete.

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| nesl.sign.neslRequestData.required | Required nesl api data for nesl sign. | The `neslData` object is missing from the request when an invitee has NeSL eSign type | Include the `neslData` object with `documentDetail`, `participants`, and optionally `stampData` |
| nesl.stamp.data.required | At least one stamp data is required for stamping flow. | stampData array is empty and participants are missing or invalid | Provide at least one entry in `stampData`, or ensure `participants` array is valid |
| nesl.participants.equal.nesl.invitees | Participants should be equal to nesl invitees. | The number of entries in `participants` doesn't match the number of NeSL-type invitees | Ensure `participants` count equals the number of invitees with NeSL eSign type |
| nesl.first.invitee.party.debtor | Invitee/Party 1 should have Contact Relation 'Debtor'. | The first participant doesn't have `contactRelation` set to `DEBTOR`, or `fullName` is missing | Set the first participant's `contactRelation` to `DEBTOR` and ensure `fullName` is provided |
| null | Invitee(N) configured mandatory for Nesl [field] verification, value is required., | NeSL verification is enabled on dashboard but the corresponding `neslConfig` field is missing | Provide all mandatory `neslConfig` verification fields (verifyPincode, verifyState, verifyYob, verifyTitle, verifyGender) |

### NeSL Document Detail Errors

### Missing Required Fields

These errors follow the pattern `neslData.documentDetail.[field].validator.invalid` or `neslData.documentDetail.[field].nullable`.

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| neslData.documentDetail.[field].validator.invalid | [field] is required for document detail. | A required documentDetail field is missing | Provide the required field. Required fields vary by `registrationType` — see below |
| neslData.documentDetail.[field].nullable | [field] is required for document detail. | A required documentDetail field is null | Provide a non-null value for the field |
| neslData.documentDetail.docRefNo.validator.invalid | docRefNo is required for document detail. | `docRefNo` is missing for `NON_LENDING` registrationType | Provide an alphanumeric `docRefNo` value |

### Enum Validation Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| registration.type.invalid | Invalid registration type. | The `registrationType` value is not recognized | Use one of: `INDIVIDUAL_LOAN`, `NON_INDIVIDUAL_LOAN`, `NON_LENDING`, `EBG` |
| debt.type.invalid | Invalid debt type. | The `typeOfDebt` value is not recognized | Use one of: `FINANCIAL`, `OPERATIONAL` |
| acount.closed.flag.type.invalid | Invalid account closed flag. | The `accountClosedFlag` value is not recognized. Note: error code has typo "acount" | Use one of: `YES`, `NO`, `ASSIGNED` |
| fund.type.invalid | Invalid fund type. | The `fundType` value is not recognized | Use one of: `FUNDED`, `NON_FUNDED` |
| sanction.currency.type.invalid | Invalid currency type. | The `sanctionCurrency` value is not recognized | Use `INR` (only accepted value) |
| credit.sub.type.invalid | Invalid credit sub type. | The `creditSubtype` value is not valid for the given `registrationType` | Use `CREDIT_FACILITY` or `PROPERTY_BUYER` for INDIVIDUAL_LOAN / NON_INDIVIDUAL_LOAN |
| event.type.invalid | Invalid event type. | The `event` value is not recognized (EBG only) | Use a valid event type value for EBG |

### Format Validation Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| nesl.field.date.error | Please enter date Of Sanction in format YYYY-MM-DD. | The `dateOfSanction` is not in the required date format | Use `YYYY-MM-DD` format (e.g., `2018-02-02`) |
| field.value.alphanumeric | Please enter the correct value of Document Reference Number in alphanumeric characters only. | The `docRefNo` contains non-alphanumeric characters (hyphens, spaces, etc.) | Use only letters and numbers (e.g., `DOCREF001` not `DOC-REF-001`) |

### NeSL Participant Errors

### Missing Required Fields

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| invitee.field.required | Mobile Number is required for NESL request for invitee N. | The participant is missing `mobileNumber` | Provide `mobileNumber` for each participant |
| invitee.field.required | Date of Birth is required for NESL request for invitee N. | The participant is missing `dob` | Provide `dob` in `YYYY-MM-DD` format |
| invitee.field.required | Official DocId is required for NESL request for invitee N. | The participant is missing `officialDocId` | Provide the document ID matching the `officialDocType` |
| invitee.field.required | Official Doc is required for NESL request for invitee N. | The participant is missing `officialDocType` | Provide one of: `PAN_CARD`, `DRIVING_LICENSE`, `VOTER_ID`, `PASSPORT`, `ANY_OTHER_OFFICIAL_ID` |
| invitee.field.required | Legal Constitution is required for NESL request for invitee N. | The participant is missing `legalConstitution` | Provide a valid `legalConstitution` value (e.g., `RESIDENT_INDIVIDUAL`, `PRIVATE_LTD`) |
| invitee.field.required | PartyType is required for NESL request for invitee N. | The participant is missing `partyType` | Provide one of: `INDIAN_ENTITY`, `RESIDENT_INDIVIDUAL`, `FOREIGN_ENTITY`, `NRI` |
| invitee.field.required | Registered Address is required for NESL request for invitee N. | Required for `NON_INDIVIDUAL_LOAN` participants | Provide `registeredAddress` for NON_INDIVIDUAL_LOAN |
| invitee.field.required | Registered Pin Code is required for NESL request for invitee N. | Required for `NON_INDIVIDUAL_LOAN` participants | Provide `registeredPinCode` for NON_INDIVIDUAL_LOAN |
| invitee.field.required | Communication Address is required for NESL request for invitee N. | Required for `NON_INDIVIDUAL_LOAN` participants | Provide `communicationAddress` for NON_INDIVIDUAL_LOAN |
| invitee.field.required | Communication Address Pin Code is required for NESL request for invitee N. | Required for `NON_INDIVIDUAL_LOAN` participants | Provide `communicationAddressPinCode` for NON_INDIVIDUAL_LOAN |

### Enum Validation Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| party.type.invalid | Invalid party type. | The `partyType` value is not recognized | Use one of: `INDIAN_ENTITY`, `RESIDENT_INDIVIDUAL`, `FOREIGN_ENTITY`, `NRI` |
| constitution.type.invalid | Invalid constitution type. | The `legalConstitution` value is not recognized | Use one of: `RESIDENT_INDIVIDUAL`, `PUBLIC_LTD`, `PRIVATE_LTD`, `LLP`, `PROPRIETORSHIP`, `PARTNERSHIP`, `ENTITY_CREATED_BY_STATUTE`, `TRUST`, `HUF`, `CO_OP_SOCIETY`, `ASSOCIATION_OF_PERSONS`, `GOVERNMENT`, `SELF_HELP_GROUP`, `NON_RESIDENT`, `FOREIGN_COMPANY` |
| invitee.field.invalid | Please enter Contact Relation valid value for invitee N. | The `contactRelation` value is not recognized | Use one of: `CREDITOR`, `DEBTOR`, `GUARANTOR`, `CO_OBLIGANT`, `SECURITY_PROVIDER`, `ASSIGNEE`, `BENEFICIARY` |
| official.doc.type.invalid | Invalid doc type. | The `officialDocType` value is not recognized | Use one of: `PAN_CARD`, `DRIVING_LICENSE`, `VOTER_ID`, `PASSPORT`, `ANY_OTHER_OFFICIAL_ID`. Note: `AADHAAR` is not valid |

### Format Validation Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| invitee.field.date.error | Please enter Date of Birth in format YYYY-MM-DD for invitee N. | The `dob` is not in the required date format | Use `YYYY-MM-DD` format (e.g., `2020-12-10`) |
| invitee.field.value.alphanumeric | Please enter the correct value of Contact Person in alphanumeric characters only for invitee N. | The `contactPersonName` contains non-alphanumeric characters (hyphens, etc.) | Use only letters, numbers, and spaces in `contactPersonName` |
| invitee.field.pan | Please enter Pan Card valid pan number for invitee N. | The `officialDocId` is not a valid PAN format when `officialDocType` is `PAN_CARD` | Provide a valid 10-character PAN number (e.g., `BHSPM9753J`) |
| invitee.field.pan.error | Please enter valid pan number(C or E as fourth letter) for invitee N. | For `NON_INDIVIDUAL_LOAN`, the PAN must be a company PAN (4th letter C or E) | Use a company PAN with C or E as the 4th character (e.g., `AABCE1234F`) |

### NeSL Stamp Data Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| neslData.stampDatas.validator.invalid | firstParty is required for stamp N | The `firstParty` field is missing in stamp data entry N | Provide `firstParty` name for each stamp data entry |
| neslData.stampDatas.validator.invalid | secondParty is required for stamp N | The `secondParty` field is missing in stamp data entry N | Provide `secondParty` name for each stamp data entry |
| neslData.stampDatas.validator.invalid | stampDutyAmount is required for stamp N | The `stampDutyAmount` field is missing in stamp data entry N | Provide `stampDutyAmount` for each stamp data entry |
| neslData.stampDatas.validator.invalid | considerationPrice is required for stamp N | The `considerationPrice` field is missing in stamp data entry N | Provide `considerationPrice` for each stamp data entry |
| neslData.stampDatas.validator.invalid | descriptionOfDocument is required for stamp N | The `descriptionOfDocument` field is missing in stamp data entry N | Provide `descriptionOfDocument` for each stamp data entry |
| neslData.stampDatas.validator.invalid | stampDutyPaidBy is required for stamp N | The `stampDutyPaidBy` field is missing in stamp data entry N | Provide `stampDutyPaidBy` for each stamp data entry |
| neslData.stampDatas.validator.invalid | articleCode is required for stamp N | The `articleCode` field is missing in stamp data entry N | Provide `articleCode` for each stamp data entry |

### NeSL Security Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| neslData.neslSecurities.validator.invalid | assetsType is required for security N | The `assetsType` field is missing in security entry N | Provide one of: `MOVABLE`, `IMMOVABLE`, `INTANGIBLE`, `NOT_CLASSIFIED` |
| neslData.neslSecurities.validator.invalid | chargeType is required for security N | The `chargeType` field is missing in security entry N | Provide one of: `MORTGAGE`, `HYPOTHECATION`, `CHARGE`, `ASSIGNMENT`, `PLEDGE`, `LIEN`, `NEGATIVE_LIEN`, `GUARANTEE`, `OTHERS`, `NOT_CLASSIFIED` |
| neslData.neslSecurities.validator.invalid | assetId is required for security N | The `assetId` field is missing in security entry N | Provide an asset ID string |
| neslData.neslSecurities.validator.invalid | securityDescription is required for security N | The `securityDescription` field is missing in security entry N | Provide a description of the security |

### NeSL Config Validation Errors

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| typeMismatch[N] | Property N is type-mismatched | A neslConfig field has an invalid value (e.g., invalid `verifyGender` like "X") | Check field values: `verifyGender` must be `M`, `F`, or `T`; `verifyYob` accepts integer or string |
| certificate.pin.code.invalid[N] | Certificate pin code is invalid for invitee N. | The `verifyPincode` is not a valid 6-digit pin code (e.g., `"ABC"`) | Use a valid 6-digit numeric pincode string (e.g., `"247667"`) |

## POST /v3.0/sign/request/reactivate — Reactivate Document

| Code | Message | Description | Solution |
|------|---------|-------------|----------|
| signinvitation.activate.success | Invitation activated successfully | *(Success — not an error)* | — |
| no.expired.invitation.found | No expired invitation exists | The document is completed, rejected, active, or already reactivated — no expired invitation to reactivate | Verify the document status before calling this endpoint. Only expired documents can be reactivated |
| no.document.found | No document found | The provided document ID does not exist | Check that the `documentId` is correct and belongs to your account |
| invalid.expiry.days.value | Invalid expiry days value | `expiryDays` is outside the valid range | Provide a value between `-1` and `365`. Use `-1` for no expiry |
| invalid.expiry.time | Invalid expiry time | `expiryTime` is in the past or is a negative timestamp | Provide a future Unix timestamp (milliseconds) for `expiryTime` |
| invalid.expiry.time.maxerror | Invalid expiry time — exceeds maximum | `expiryTime` is more than 365 days from now | Provide an `expiryTime` within 365 days from the current date |