> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eazecustoms.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Resubmit a rejected movement

> Resubmit a rejected movement with corrected payload fields.

Resubmit a movement with status `REJECTED`.

### Path Parameters

<ParamField path="id" type="string" required>
  Shipment Public ID (`shp_…`).
</ParamField>

<ParamField path="movementId" type="string" required>
  Movement Public ID (`mov_…`).
</ParamField>

### Headers

<ParamField header="Idempotency-Key" type="string" required>
  Unique key that makes retrying this request safe for 24 hours. A UUID is recommended.
</ParamField>

### Body

<ParamField body="quantity" type="integer" required>
  Corrected package quantity.
</ParamField>

<ParamField body="grossWeightKg" type="number" required>
  Corrected gross weight in kilograms.
</ParamField>

<ParamField body="customsSupervision" type="string" required>
  Whether the goods are under customs supervision: `Y` (yes) or `N` (no).
</ParamField>

<ParamField body="goodsHandlingCode" type="string" required>
  PGTS goods-handling status:

  * `N` — not applicable (the ordinary case)
  * `A` — export under Inward Processing Relief (IPR)
  * `H` — trade policy measures apply in the customs-free zone
  * `B` — IPR goods subject to trade policy measures
  * `G` — goods undergo a usual form of handling in the customs-free zone
  * `C` — IPR goods that underwent a usual form of handling
</ParamField>

<ParamField body="hawbId" type="string">
  HAWB Public ID (`hawb_…`).
</ParamField>

<ParamField body="partyId" type="string">
  RTO party Public ID (`rpty_…`). Required when the original action needs a party (`VAH`, `VAB`, `ISL`, `USL`).
</ParamField>

<ParamField body="customsDeclaration" type="object">
  Corrected customs declaration, following the original movement's action. Required for `VAH`, `VAB`, `ISC` and `USC` unless one is already on file (for example, an allocation or the configured RTO licence). Not allowed for `ISL` and `USL`, which reuse the linked movement's declaration. The fields depend on `source`:

  <Expandable title="properties">
    <ParamField body="source" type="string" required>
      Where the declaration comes from. Allowed values: `INTERNAL`, `EXTERNAL`, `RTO_LICENSE`, `DECO`, `ENTREPOT`. `VAH`/`VAB` accept `EXTERNAL` or `RTO_LICENSE`; `ISC` accepts `INTERNAL`, `EXTERNAL` or `ENTREPOT`; `USC` also accepts `DECO`.
    </ParamField>

    <ParamField body="declarationId" type="string">
      `INTERNAL` only, required. Declaration Public ID (`dec_…`) on this shipment with an accepted MRN.
    </ParamField>

    <ParamField body="documentType" type="string">
      Required for `EXTERNAL` and `ENTREPOT`. PGTS document type, for example `X` (full declaration).
    </ParamField>

    <ParamField body="declarationType" type="string">
      `EXTERNAL` only, required. Declaration type, for example `IM`, `EX` or `T1`.
    </ParamField>

    <ParamField body="declarationNumber" type="string">
      `EXTERNAL` only, required. MRN or other customs reference.
    </ParamField>
  </Expandable>

  `RTO_LICENSE` and `DECO` take no other fields, and `ENTREPOT` only `documentType`: the licence or permit number comes from your RTO configuration. Any field not listed for the chosen source is rejected.
</ParamField>

```json JSON Payload theme={null}
{
  "quantity": 10,
  "grossWeightKg": 405,
  "customsSupervision": "Y",
  "goodsHandlingCode": "N",
  "partyId": "rpty_3f9a1c0e5b7d4e2f8a6c1b9d0e3f7a25"
}
```

<ResponseExample>
  ```json 200 OK theme={null}
  {
    "movementId": "mov_3f9a1c0e5b7d4e2f8a6c1b9d0e3f7a25",
    "shipmentId": "shp_3f9a1c0e5b7d4e2f8a6c1b9d0e3f7a25",
    "action": "ISL",
    "status": "QUEUED",
    "processType": "IMPORT_HANDLING",
    "trigger": "API",
    "originalMovementId": null,
    "createdAt": "2026-06-10T08:30:00.000Z",
    "updatedAt": "2026-06-10T09:15:00.000Z"
  }
  ```
</ResponseExample>