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

# Void parcel

> The Void Parcel API lets you take out a declared parcel if you do not intend to send it or if it needs to be updated due to changed shipment requirements.

<Note>
  Part of the [Shipping Documents API](/shipping-documents-api) integration guide — see it for when and how to use this endpoint.
</Note>


## OpenAPI

````yaml api-reference/specs/voidparcel.yaml POST /Parcel/VoidParcel
openapi: 3.0.3
info:
  title: VoidParcel
  version: 1.0.0
  description: >-
    The Void Parcel API lets you take out a declared parcel if you do not intend
    to send it or if it needs to be updated due to changed shipment
    requirements.
servers:
  - url: https://{globale_api_domain}
    variables:
      globale_api_domain:
        default: globale_api_domain
        description: Global-e API host, supplied to the merchant by Global-e.
security: []
tags:
  - name: VoidParcel
    x-page-title: VoidParcel
  - name: 'Direction: Merchant → Global-e'
  - name: 'Domain: Shipping'
paths:
  /Parcel/VoidParcel:
    post:
      tags:
        - VoidParcel
      summary: Void a declared parcel
      description: >-
        The Void Parcel API lets you take out a declared parcel if you do not
        intend to send it or if it needs to be updated due to changed shipment
        requirements. At least one order ID should be provided in the request —
        the Global-e OrderId or the merchant's MerchantOrderId.
      operationId: voidParcel
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/VoidParcelRequest'
            example:
              OrderId: '#12354'
              ParcelCode: '454234'
              MerchantOrderId: '#1138'
      responses:
        '200':
          description: >-
            Result of the void request. Object-level problems are reported in
            the body with the Errors array populated; IsSuccess can still be
            true for a logged shipper-cancel failure (code C102).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/VoidParcelResponse'
              example:
                IsSuccess: true
                Errors: []
components:
  schemas:
    VoidParcelRequest:
      type: object
      title: VoidParcelRequest
      required:
        - OrderId
        - ParcelCode
      properties:
        OrderId:
          type: string
          description: Order unique identifier.
        ParcelCode:
          type: string
          description: Code used to identify the ParcelCode to void.
        MerchantOrderId:
          type: string
          description: The merchant's order unique identifier.
    VoidParcelResponse:
      type: object
      title: VoidParcelResponse
      properties:
        IsSuccess:
          type: boolean
          description: Indicates whether the parcel was voided successfully.
        Errors:
          type: array
          description: >-
            Error entries; empty on success. Documented Void Parcel error codes
            are C100 and C101 (parcel cannot be voided due to its status), C102
            (parcel voided but the shipper's cancel API failed — logged, with
            IsSuccess still true), C103 (internal unknown failure), and C104
            (parcel code not found or already voided).
          items:
            type: object

````