API

Logistics APIs

GET logistics/shipments/{shipmentId}/packages/{packageId}

Package details for provided identifier

HTTP method GET
URI https://api.rambase.net/logistics/shipments/{shipmentId}/packages/{packageId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {shipmentId} Shipment identifier
Long, minimum 1000000
- URI parameter {packageId} Package identifier
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 2716, version 10

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
1

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]
$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json"
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$select String, optional Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select page for more information.

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<Package>
2
     <PackageId
PackageId

Package identifier

>
{Integer}</PackageId>
3
     <Weight
Weight

Weight of this package. Measurement unit is specified in the location arthive

>
{Decimal}</Weight>
4
     <Comment
Comment

Comment for this package

>
{String}</Comment>
5
     <Tracking>
6
          <TrackingNumber
TrackingNumber

Tracking number for this package

>
{String}</TrackingNumber>
7
          <TrackingUri
TrackingUri

Tracking uri for the package. The uri is generated based on set-up in the archive of tracking number series, and might include the tracking number

>
{String}</TrackingUri>
8
     </Tracking>
9
     <Freight>
10
          <Currency
Currency

Three character code following the ISO 4217 standard

>
{String}</Currency>
11
          <NetPrice
NetPrice

The freigth price for this package

>
{Decimal}</NetPrice>
12
          <Cost
Cost

Freight costs of this package

>
{Decimal}</Cost>
13
     </Freight>
14
     <Dimensions>
15
          <Height
Height

Height of this package. Measurement unit is configured in the location archive.

>
{Decimal}</Height>
16
          <Length
Length

Length of this package. Measurement unit is configured in the location arhive

>
{Decimal}</Length>
17
          <Width
Width

Width of this package. Measurement unit is specified in location archive.

>
{Decimal}</Width>
18
          <Volume
Volume

Volume of this package. The volume is not necessarily simply the product of length, width and height, this only applies for cuboid packages. Therefore the system only proposes this simple calculation if length, width and height are filled and the volume is still empty; but as soon as already a value exists there, it will not be changed automatical any more, for it could have been especially entered for this package.

>
{Decimal}</Volume>
19
     </Dimensions>
20
</Package>
1
{
2
     "package": {
3
          "packageId
PackageId

Package identifier

":
"{Integer}",
4
          "weight
Weight

Weight of this package. Measurement unit is specified in the location arthive

":
"{Decimal}",
5
          "comment
Comment

Comment for this package

":
"{String}",
6
          "tracking": {
7
               "trackingNumber
TrackingNumber

Tracking number for this package

":
"{String}",
8
               "trackingUri
TrackingUri

Tracking uri for the package. The uri is generated based on set-up in the archive of tracking number series, and might include the tracking number

":
"{String}"
9
          },
10
          "freight": {
11
               "currency
Currency

Three character code following the ISO 4217 standard

":
"{String}",
12
               "netPrice
NetPrice

The freigth price for this package

":
"{Decimal}",
13
               "cost
Cost

Freight costs of this package

":
"{Decimal}"
14
          },
15
          "dimensions": {
16
               "height
Height

Height of this package. Measurement unit is configured in the location archive.

":
"{Decimal}",
17
               "length
Length

Length of this package. Measurement unit is configured in the location arhive

":
"{Decimal}",
18
               "width
Width

Width of this package. Measurement unit is specified in location archive.

":
"{Decimal}",
19
               "volume
Volume

Volume of this package. The volume is not necessarily simply the product of length, width and height, this only applies for cuboid packages. Therefore the system only proposes this simple calculation if length, width and height are filled and the volume is still empty; but as soon as already a value exists there, it will not be changed automatical any more, for it could have been especially entered for this package.

":
"{Decimal}"
20
          }
21
     }
22
}

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 101013 HTTP 404 Sub-module not found
Error 101420 HTTP 404 Setting definition not found