Changelog
Back to All

v1.039

about 2 hours ago

The specification now shows which string fields must contain a non-whitespace character.
The API already rejected an empty or whitespace-only value for these fields with 400. The specification did not show this rule. Now these fields have "pattern": "\\S". The API behavior does not change.

🚀 New Endpoints

None

🛠 Schema & Property Updates

None

📖 Documentation & Constraints Changes

These fields now have pattern: \S. A value must contain at least one character that is not whitespace:

  • Create or Update Receiving (POST /v1/integrations/receiving):
    • warehouse, asn, receiving_key
    • tracking_numbers[]
    • items[].carton_key, items[].loose_units_pallet_key
    • cartons[].carton_key, cartons[].pallet_key, cartons[].identifiers[].value
    • pallets[].pallet_key, pallets[].identifiers[].value
  • Create Inventory Hold (POST /v1/integrations/inventory-hold): asn
  • Retrieve List of Inventory Holds (GET /v1/integrations/inventory-holds-list): query parameter asn
  • Create or Update Order (POST /v1/integrations/order): items[].name

No endpoints, fields or enum values were added or removed. The API accepts and rejects the same requests as before, so integrations need no change.