In this release, we’ve expanded our data coverage by adding support for UK ZIP codes in the Geocoding API and incorporating the new Mediterranean ECA (Emission Control Area) zone across our APIs.

We’ve also addressed a couple of issues to improve reliability and consistency throughout our APIs.

⚡️ What's new

Support for UK ZIP codes added to Geocoding API

The Geocoding API now includes full support for UK ZIP codes, thanks to the integration of a dedicated dataset.

You can now query specific UK ZIP codes like AB101BW or CR05DG using either of the following endpoints:

• /geocoding/v2/zipcode?country=GB&postal=AB101BW
• /geocoding/v2/all?postalCode=AB101BW

Example response:

{
    "type": "FeatureCollection",
    "features": [
        {
            "type": "Feature",
            "properties": {
                "name": "George St/Harbour, Aberdeen City",
                "countryCode": "GB",
                "state": "Scotland",
                "country": "United Kingdom",
                "postalCode": "AB101BW",
                "type": "zipcode"
            },
            "geometry": {
                "type": "Point",
                "coordinates": [
                    -2.097003936767578,
                    57.149051666259766
                ]
            }
        }
    ],
    "properties": null
}

Explore both endpoints:

• Geocoding to find all types of locations
• Geocoding to find the geocoordinates of a zipcode

Also available in the Shipment API

The /shipment/v2/report/co2 endpoint now accepts UK ZIP codes as valid origin and destination inputs.

Try it out here.

What’s next?

We’re planning to enhance query flexibility by normalizing UK postcode input, so whether users include a space (e.g. AB10 1BW) or not (e.g. AB101BW), results will remain consistent. This improvement is scheduled for a future cycle.

Mediterranean Sea Now Supported as an ECA Zone (MED ECA Zone)

As of May 1st 2025, the Mediterranean Sea has officially become a Sulphur Emissions Control Area (SECA) under MARPOL Annex VI. This update is now reflected in our APIs, and no action is required on your end.

✨ Key updates include:

• Routing API now returns secaIntersection=true or routes within the Mediterranean that previously did not cross other SECA zones (e.g. the North Sea or the Baltic Sea).
• For CO₂ and Shipment API users, you may notice small changes in emission results. That’s because our vessel models now factor in the use of low-sulphur fuels in the Mediterranean. However, since these fuels have similar carbon emissions to VLSFO, the impact on reported emissions will be minimal, typically less than 3% for the Mediterranean leg of a shipment. Ships using scrubbers or low-sulphur fuels like LNG won't see any changes.
• If you had enabled the MED ECA zone via the versioning feature of our Routing API, you can now revert to default settings.
• This change may also influence carrier operational costs and freight rates, though it doesn’t affect carbon factors for vessels using scrubbers or LNG.

Learn more in this article or reach out our support team [email protected] if you have any questions.

🛠️ Fixes and improvements

Air emissions totals

We’ve fixed a regression in our air emissions calculations from the Shipment API /shipment/v2/report/co2 where the reported co2e.total didn’t match the sum of co2e.ttw and co2e.wtt.

This issue was quickly identified and fixed, and is now covered by additional tests to prevent future inconsistencies.

Locations ordered by distance in/geocoding/v2/closest

Previously, this endpoint returned results influenced by location size (e.g., large airports ranked first), rather than pure distance. This has been corrected, results are now consistently ordered by distance as expected.

📘

You made it to the end of our changelog, thanks for reading 👏🏼

We'd love to hear your thoughts on these updates. Send us your feedback at [email protected]!