Skip to main content
POST
Create a movement
Create a movement by action (VAH, VAB, ISL, USL, ISC, USC). Do not send a provider, configuration, or process type — both come from the shipment.

Path Parameters

string
required
Shipment Public ID (shp_…).

Headers

string
required
Unique key that makes retrying this request safe for 24 hours. A UUID is recommended.

Body

string
required
Movement action. Allowed values: VAH, VAB, ISL, USL, ISC, USC.
integer
required
Number of packages (colli) moved.
number
required
Gross weight of those packages, in kg.
string
required
Whether the goods are under customs supervision: Y (yes) or N (no).
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
string
HAWB Public ID (hawb_…). Omit for the master AWB.
string
RTO party Public ID (rpty_…). Required for VAH, VAB, ISL, and USL.
object
Customs declaration for the movement. 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: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.