v1.013

Adds support for tracking numbers on POST /v1/integrations/receiving, mirroring the existing tracking-number capability on the internal/draft receiving endpoints. Unblocks integrations (e.g. small-parcel ASNs) that need to send their carrier tracking numbers up-front.

🚀 New Endpoints

None

🛠 Schema & Property Updates

• Create Or Update Receiving Input — added an optional tracking_numbers field at the top level:
  • tracking_numbers (array<string>|null) — list of tracking numbers for the receiving's packets. Each item is a string up to 255 characters. Accepts absent or null (no change), [] (clear all), or a populated list (replace all).

📖 Documentation & Constraints Changes

• Field semantics on POST /v1/integrations/receiving:
  • Create: the provided list is set as the receiving's tracking numbers; omitting the field results in no tracking numbers.
  • Update: omitting the field leaves existing tracking numbers untouched (preserving backwards compatibility for current integrations); an empty list clears them; a populated list replaces them. Removing a tracking number that has already been checked in is rejected with a 400 (InvalidReceivingPacketTrackingNumberException).