The Tracking Webhook system has been updated to classify all HTTP responses from the carrier API outside the HTTP 200-299 range as errors and return the corresponding error response. Additionally, the retry mechanism has been revised to cease retry attempts to fetch tracking data from the carrier API after 24 hours of continuous failure, following specific retry intervals.

The information about manifested containers is now stored in the database for future reference. A new field called ‘Container Status’ has been added to all the relevant Container APIs to store and retrieve the container information based on status. The ‘Container Status’ can either be ‘Active’ or ‘Manifested’. Customers can only add or remove shipments from containers with an ‘Active’ status. Containers can only be manifested if they have an ‘Active’ status. Containers in the ‘Manifested’ status cannot be deleted. For example, in the Get Containers API, the query parameters in the API request have been updated to include the optional parameter 'containerStatus,' and the API response now includes the containerStatus field populated with the container's status, either 'Active' or 'Manifested'. For more information on managing shipments in a container, please refer to the API reference page and the Sapient Core API section.

The Swagger Documentation for the Royal Mail Get Collections Timeslot endpoint has been updated in the Section Description. This section now includes information on creating collections, obtaining collection timeslots, and cancelling collections for Royal Mail shipments.

The Type 3 pre-advice file has been updated to include Container ID. For shipments in a container, the Detail Supplement Record (03) is populated with the supplement code "SO" and the Container ID (truncated to 40 characters if necessary). For shipments not in a container, the Detail Supplement Record (03) will not contain the supplement code “SO”.

Create Shipment endpoint has been updated to include USA Army Post Office (APO) county codes for destination address.

The destinations include:

• Armed Forces Pacific (County Code - AP)
• Armed Forces Europe (County Code - AE)

The Create Shipment endpoint now includes four unincorporated territories:

• The Virgin Islands
• American Samoa
• Guam
• The Northern Mariana Islands

📘

IMPORTANT:

The State Code on the label uses the ISO Country Code from the request, and the Country on the label is USA. The billing code follows the service billing code for the USA.

The following services have been removed. These services have already been archived and no longer in use.

• BG3, BP3, DG3, DG6, IE3, IG3, IG6, IP3, IP6, MB3, PS6, PS8, WE3, WG3, WG6, WP3, DP4, IP4, WP4, OZ1, OZ3, OZ4, OZ6, WW1, WW3, WW4, DE1, DG1, DP1, HVC and HVF

📘

Please Note:

These services are no longer available for shipment creation.

New import services:

• ITI, ITJ, DE9, DEO, DEP, DEQ, DER, DEU, DEV, DEX, DEY, DEZ, DE5, DE7, and DE8.
• These services come with domestic labels as shipments created with these services are entering Great Britain from international locations. All these services are closed, requiring a service contract for use.

New international cross-border:

• DE0, ITO, ITQ, ITT, ITV, ITW, IYX, ITY, ITZ, IT1, IT5, IT6, IT7, IT8, IT9, IT0, TIF, and TIH.
• These services come with international labels. All these services are closed and require a service contract for use.

Swagger documentation has been updated as per below:

• Create Shipment API - The County field description has been revised to specify that when provided for the USA, Australia, and Canada, it must contain a valid state code or name.
• Create Shipment API - The description for the SpecialistPhoneNumber field has been revised and highlighted in bold for customer reference.

New International Extra-Territorial Office of Exchange (ETOE) services have been added. The list of services added are ETK, ETL, ETM, ETN, ETO, ETP, ETQ, ETR, ETG, ETH, ETI, ETA, ETB, ETC, ETD, ETE, and ETF. These services require a service contract and utilize the International Label template. They are classified as either Personal Correspondence or Non-Personal Correspondence services. The Get Carrier Services API can be called to retrieve the service descriptions. See the API Reference Page and Carriers API section for details.