GETMethod GET/distributor-portal/shipments/{shipment_id}

You read back one of your shipments by its id: its units (serial, lot) and the history of its goods-in confirmations.

⛔ Isolation. A shipment of another distributor — of the same brand or of another — answers exactly 404, the same answer as a shipment that does not exist. This call never confirms that another distributor's shipment exists.

#Authorization

Session of a distributor contact account. See GET /distributor-portal/me.

#Rate limit

30 calls a minute, shared with the rest of the distributor portal.

#Path and query parameters

#Example request

curl -i "https://api.sealtrust.io/v1/distributor-portal/shipments/318" \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.0000000000000000000000000000.0000000000000000000000000000"

#Example response

{
  "id": 318,
  "order_ref": "SO-2026-0318",
  "status": "closed",
  "ship_date": "2026-10-01",
  "units_allocated": 2,
  "received": true,
  "receptions": [
    {
      "id": 7,
      "received_at": "2026-10-05T08:30:00Z",
      "received_by": "Camille Exemple",
      "scanned_count": 2,
      "note": null
    }
  ],
  "units": [
    {
      "product_id": 9001,
      "serial": "DSP000000123",
      "product_name": "Eau de parfum 50 ml",
      "lot": "LOT-2026-09-A",
      "allocated_at": "2026-09-28T09:12:00Z"
    }
  ],
  "units_total": 2,
  "page": 1,
  "page_size": 50
}

#What you never find here

No consumer personal data, no information about another distributor, no brand-internal note. Units are read by product id, serial and lot — never by who scanned them nor where they go next.

#Errors

#See also

• POST /distributor-portal/shipments/{shipment_id}/receive, confirm the reception.