Skip to main content

Reverting Field Names in Shipment Order API Endpoints

Dear Valued Customer,

We are writing to provide an important update regarding recent changes to the Logiwa OpenAPI and the steps we are taking to ensure the continued stability of your integrations.

What Happened?

During our system release on April 12, 2026, an unintentional change was introduced to the naming convention of two specific fields within the products segment of our Shipment Order API responses. This change affected the following endpoints:

  • Get Shipment Order: /v3.1/ShipmentOrder/{identifier}

  • List Shipment Orders: /v3.1/ShipmentOrder/list/i/{index}/s/{size}

Specifically, the fields were renamed as follows:

  • packType was changed to linePackTypeName

  • packTypeIdentifier was changed to linePackTypeIdentifier

Our Action (Reverting to Original State)

To maintain backward compatibility and prevent any long-term disruption to your automated workflows, we deployed a hotfix on April 21, 2026, to restore the following naming convention:

  • linePackTypeName will revert to packType

  • linePackTypeIdentifier will revert to packTypeIdentifier

Action Required & Recommendations

Depending on how your system handles API responses, we recommend the following actions:

  • Audit for Potential Data Gaps: If your integration did not adapt to the temporary names between April 12 and April 21, certain data (Pack Type information) may not have been captured correctly in your local system during this period. We strongly recommend reviewing any Shipment Orders processed during this window to ensure data integrity.
    ​
    ​

  • Revert Logic Adjustments: If your technical team adjusted your integration logic to accommodate the temporary field names, please ensure your system is updated to use the original names (packType and packTypeIdentifier) following today's deployment.

We apologize for this unintentional change and any inconvenience it may have caused. If you have any questions, please do not hesitate to reach out to our support or integration teams.

Did this answer your question?