Shipment
The heart of the Integrated Services Platform are shipments. The definition of shipments consists of:
sender and recipient data
shipment (one or more), which will be physically shipped
selected service (optional added services)
other additional attributes dependent on user preference, eg.:
Insurance
Cash collection
To create a shipment ready for shipping, 3 steps are required:
Creating the shipment, consisting of recipient and sender details and information about the shipment itself (purple figures on the diagram below)
Downloading the information about the available services for the created shipment (blue figures on the diagram below),
Purchasing a label by selecting a service available for the shipment from step 1 (green figure on the diagram below)
Service prices may differ based on the shipment dimensions and parameters defined upon creation.
The list of all available services can be found in https://dokumentacja-inpost.atlassian.net/wiki/spaces/PL/pages/18153507
Service availability depends on the carriers with which the organization has signed contracts with.
For Clients whose agreement allows for a debit to be created in the InPost system (debit client), prices will not be returned to the JSON response to the request sent to the API.
On this page
Shipment creation diagram
Structure
Shipment resource has the following attributes:
Attribute | Type | Description |
|---|---|---|
| Integer | Read only. Shipment identifier in ShipX. |
| String | Read only. Current shipment status. |
| String | Shipment tracking number (logistic system ID). |
| String | Return shipment number. Will only appear if the shipment has received a status of
"href": "https://api-shipx-pl.easypack24.net/v1/shipments/123456789",
"id": 123456789,
"status": "returned_to_sender",
"tracking_number": "523000015611700083038270",
"return_tracking_number": "522107010621008001205984",
"service": "inpost_courier_standard",
...The number is also returned in webhook notifications https://dokumentacja-inpost.atlassian.net/wiki/spaces/PL/pages/18153630/Webhooki#Dane-wysy%C5%82ane-w-przypadku-gdy-przesy%C5%82ka-otrzyma-status-ZDN-(Zwrot-do-Nadawcy---returned_to_sender) |
| String | The service selected by the customer. Available values https://dokumentacja-inpost.atlassian.net/wiki/spaces/PL/pages/18153507. |
| String | Additional shipment description, e.g. order or client ID |
| Boolean | Determines whether the shipment is a return. Dedicated parameter for services: |
| Integer | Unique application identifier. |
| Integer | If of the user that created the shipment, if logged in. |
| String | ID of the broker generating the shipment within a different organization. |
| String | Duplicate of |
| Boolean | Determines if the shipment has a service “Service Weekend shipments”. |
| String | Any comment. |
| String | Place of cost creation. |
| Array[String] | Additional services selected when creating the shipment (different offers may contain different additional services). Available additional services: |
| CustomAttributes | Additional, optional shipment attributes. |
| MoneyData | Cash collection for the shipment. |
| MoneyData | Shipment insurance. |
| Peer | Sender details. |
| Peer | Recipient details. |
| Offer | The service selected when buying the label. |
| Array[Offer] | List of available services with prices, which can be purchased for the shipment. |
| Array[Transaction] | List of payment transactions related to the shipment. |
| Array[Parcel] | List of parcels within the shipment. |
| DateTime | Read only. Shipment creation date in ShipX. |
| DateTime | Read only. Shipment update date in ShipX. |
Parcel object attributes:
Attribute | Type | Description |
|---|---|---|
| String | Required when creating a shipment with multiple parcels. Unique parcel ID within the shipment that allows for validation errors to be returned in connection to a specific parcel. ID is not persisted in the database and is not returned as an attribute of an already created shipment. |
| String | Predefined dimension and weight template name. The list of predefined dimension and weight templates can be found in https://dokumentacja-inpost.atlassian.net/wiki/spaces/PL/pages/18153507 |
| Object | Shipment dimensions.
Filled automatically when selecting a valid |
| Object | Shipment weight
Filled automatically when selecting a valid |
| String | Shipment tracking number. Assigned when buying a selected offer. |
| Bool | Set to Parcel handled only within the domestic courier services, in which one of its dimensions exceeds 120 cm, or the sum of the dimensions (length + width + height) exceeds 220 cm. Additionally, parcels considered non-standard are: round, cylindrical or oval, irregular shaped and/or with protruding elements. |
Offer object attributes:
Attribute | Type | Description |
|---|---|---|
| Integer | Unique offer identifier in the context of the shipment. |
| Service | Offered service object. |
| Carrier | Carrier object. |
| Array[String] | Additional services selected when creating the shipment - available within the offer. |
| String | Offer status. Available offer statuses: |
| DateTime | Date and time when the offer expires. |
| Decimal | Service price. |
| String | Currency of the service price. |
| Array | Offer unavailability reasons. |
Service object attributes:
Attribute | Type | Description |
|---|---|---|
| String | Service ID |
| String | Service name |
| String | Service description |
Carrier object attributes:
Attribute | Type | Description |
|---|---|---|
| String | Carrier ID |
| String | Carrier name |
| String | Carrier description |
Transaction object attributes:
Attribute | Type | Description |
|---|---|---|
| String | Transaction ID |
| String | Transaction status. Available statuses: |
| DateTime | Transaction creation date and time. |
| DateTime | Last transaction modification date and time. |
| Integer | ID of the offer connected to the transaction. |
Peer object attributes:
Attribute | Type | Description |
|---|---|---|
| String | Peer ID |
| String | Peer name |
| String | Company name |
| String | First name |
| String | Last name |
| String | E-mail address |
| String | Telephone number |
| Address | Address |
Address: object attributes:
line1 and line2 attributes are still supported, however, usage of street and building number is recommended.
Attribute | Type | Description |
|---|---|---|
| String | Address ID |
line1 | String | Address first line |
line2 | String | Address second line |
| String | Street name |
| String | Building number |
| String | City |
| String | Postal code |
| String | Country code |
MoneyData object attributes:
Attribute | Type | Description |
|---|---|---|
| Decimal |