👋 Happy new year folks, we hope your break was restful! We are now well into 2023 and our team is excited to unveil a first few set of features and fixes.

Recall that [last release] (https://developer.searoutes.com/changelog/cycle-5-updates-q4-2022) we introduced our /shipment/v2/CO2 API, which can be used to estimate the carbon footprint of a door to door movement, for either a container (FCL) or parcel (LCL).

Our shipment API is now one of our most used APIs and supports:

locations as (un)locodes, IATAs, city names or zipcodes
multimodal itineraries, with pre and on carriage
LCL/LTL and FCL with typical ISO codes, including reefers (20GP, 40GP, 40HC, 22R1, 42R1, etc.)
various typologies of bookings, i.e. 3 x 40 foot HC & 2 x 20 foot GP

📣 This release, we're super excited to announce the beta release of our /asset/V2/run/CO2 API, geared towards fleets and distribution centers. We've also extended our Shipment endpoint to support specific carriers, and published a few fixes to our web app.

✨ New & Improved.

🆕 Asset run API (beta)

This endpoint calculates the CO2 emissions both of the asset and the parcels it transports, from pick-ups to deliveries, also called milk-run for trucks. For this to work, we have developed a new model for road emissions 🚚. This model:

specifies and allocates empty running distances to each parcels
adjust the load factor of the truck automatically along the run, between each pickup or delivery location.
returns both the carbon emissions of the asset for the owner and the parcels for the beneficiary cargo owner.
As previously available our our /shipment/v2/co2 endpoint, users can specify the weight of parcel, and the specifics of the asset, i.e size of truck and type of fuel.

You can read the documentation of that endpoint here.

Shipment & CO2 APIs

We now support specific road carriers in North America on our [/shipment/v2/co2] (https://developer.searoutes.com/reference/getco2forshipment) endpoint and [/co2/v2/direct] (https://developer.searoutes.com/reference/getco2forvessel) endpoints.
Likewise, we now support passing carrier SCAC codes on our /shipment/v2/co2 for ocean legs. This is especially useful when not knowing the vessel on which the booking was executed.
Following high demand, we have added the possibility to pass a distance to all of our CO2 endpoints. It's now possible to bypass Searoutes' distance engine, so you can use the raw data of your telematics or GPS tracks.

🛠 Fixes & Updates.

Better exception handling on our /vessel/v2 API.
Fix payloads issues on our [/shipment/v2/co2] (https://developer.searoutes.com/reference/getco2forshipment) endpoint.
Truck size not mandatory when weight is passed on /shipment/v2 and /co2/v2/direct/road.

👀 Preview of Cycle 7

This upcoming cycle, we'll continue the work started on API onboarding and trial.
We have been working on a major update of our CO2 emission models for ocean shipments. We expect the first bricks to be released this 23Q1.
We'll publish some adjustments to our road CO2 emission models, with improvements in the way we handle ferries.