API service

Optimization, inside your own systems

All OV optimization types delivered through a fully documented API. RTZ returned for ECDIS, URL push on completion, and full integration of your own consumption models.

Capability

What the API delivers

All optimization types

Minimum cost, on time arrival, CP operation, earliest and latest arrival. Wind-assisted propulsion coming later in 2026.

WMS weather layers

Weather map layers inside your existing platform.

Fully documented

Continuously updated documentation for seamless operations.

The lowest combined cost of TCE and fuel, with flexible arrival. Variable speed and engine load; the most commercial arrival time is found for you.

Minimized fuel while the required ETA is maintained, with weather-corrected speeds through the voyage.

CP-defined daily consumption target with reduced weather impact; slow steaming option for rough weather avoidance.

Arrive as early or late as weather safely allows; be first at the load or discharge port, or optimize timing when availability varies.

Coming later in 2026. Routing and speed optimization for vessels with wind-assisted propulsion.

REST API · RTZ for ECDIS · URL push on completion · External consumption models per vessel · WMS weather layers · Guided onboarding
Why an API

Why an API, not another platform?

Most routing products ask your team or your customers to adopt yet another standalone system. The Optimum Voyage API takes the opposite approach: the optimization comes to you, inside the systems your operators, charterers, performance teams and customers already use.

No additional platform

Nothing new for your users or customers to manage.

No parallel workflow

One operational process, not two running side by side.

No repeated data entry

Voyage data is entered once, in your own system.

No tool replacement

Existing fleet-management systems stay in place.

No engine to maintain

The optimization technology is built and run by us.

Your software remains the interface and the centre of the customer experience. Optimum Voyage provides the optimization technology behind it.

Use cases

What can you build with it?

The API works as the optimization engine behind a wide range of maritime products and operational workflows.

Native optimization module

A voyage optimization module inside your existing maritime platform, without building the engine behind it.

White-label routing service

Weather routing and optimization delivered under your own brand and customer experience.

Fleet-wide daily optimization

An automated route and speed recommendation process across the whole fleet, updated daily.

ETA and fuel forecasting

Weather-corrected arrival and consumption forecasts inside dashboards, alerts and reports.

Commercial voyage planning

Evaluate alternative routes, speeds and arrival times before fixing the voyage.

Decision support for operators

Recommendations delivered straight to operators, charterers and performance teams.

How it works

Basic voyage data in, optimized routes out

Send us the voyage; vessel, ports, departure and optimization type. We return the optimized route, speeds and consumption, with an RTZ file for ECDIS. Your system is notified the moment each result is ready, and every voyage is re-optimized daily until arrival.

Every integration is set up together with our team; the scope is small and most are live within a short period, not months.

Aerial view of a vessel underway at sea
Integration flow

From vessel setup to daily re-optimization

01

Configure the vessel

Connect the vessel with the right performance model: an Optimum Voyage model, a partner model or a combination.

02

Submit the voyage

Vessel, ports, departure timing, arrival requirements and the selected optimization objective. The request is validated before calculation begins.

03

Run the optimization

Route and speed combinations are evaluated against vessel performance, forecast weather, currents and commercial priorities.

04

Webhook notification

Your system is notified the moment the optimization result is ready.

05

Retrieve and display

The structured result is retrieved through the API and presented inside your own application, map, report or workflow.

06

Repeat until arrival

The voyage is re-optimized daily as the vessel progresses and new forecasts become available.

The result includes
Optimized route and waypointsRecommended speed profileExpected arrival timeExpected fuel consumptionVoyage duration and distanceEngine-load profileAlternative voyage scenariosECDIS-compatible RTZ routeUpdated results after each re-optimization
Integration

Integration options

External consumption models

Full integration of external consumption models as the foundation for any optimization; models added per vessel through the OV API.

API integration

OV optimizations are built to integrate easily into any system, custom or commercial; results are returned with all information needed to build into any maritime system.

Flexible delivery during rollout

Nothing needs to be fully automated from day one: voyages can be appointed via portal, email or API, and results delivered the same way while the integration is completed.

Results are delivered where you need them: on the portal, in daily reports featuring partner and OV logos, or as an API response. Daily communications can be run by the OV ops team or shared with the partner for redistribution.

Vessel models

Your consumption model, or ours

The quality of any optimization depends on the vessel model behind it. The API supports different modelling setups, applied vessel by vessel, so mixed fleets and different customer requirements run through the same integration.

OPTION 01

Full Optimum Voyage model

A vessel-specific energy or speed/consumption model, reflecting how the vessel performs at different speeds, drafts, engine loads and weather conditions.

OPTION 02

Hybrid model

Your own calm-water consumption model, combined with Optimum Voyage weather-impact modelling and the optimization engine.

OPTION 03

Full partner model

A complete energy or speed/consumption model supplied by you. Relevant for performance-management providers and analytics platforms that maintain their own models.

Who it's for

Built for platforms and in-house systems

Platforms and maritime software providers

Add routing value for your clients, delivered through your own product.

Owners and operators with in-house systems

Optimization without switching tools; results land in the systems your team already uses.

WMS layers

Forecast layers, built into your platform

Wind, waves, swell and currents rendered as WMS layers in your existing platform; the same forecasts the optimization runs on, with point data on click.

Waves Sea wavesSwell wavesCombined waves
Conditions Wind speedCurrentsPressure at sea level
Overlays Wind barbsHurricane tracker

Want the full layer set and integration details? Get in touch and we will walk you through it.

Proof

Results with TORM

TORM integrates in-house BI data, weather insights and Optimum Voyage optimization technology into its own operational workflow. Captains retain full control; data-driven recommendations are balanced with seamanship, voyage by voyage.

The results below were measured across live commercial voyages. The same optimization technology behind them is what the API delivers into partner platforms and operational systems.

10%
fuel savings
13%
less time in bad weather
1-2%
faster voyages

Want the same evidence for your own fleet or platform? We run representative voyages through the API and review route quality, speeds, consumption and ETA performance together with your team, before you commit development resources.

FAQ

Frequently asked questions

Do we need to use an Optimum Voyage vessel model?

No. You can use an Optimum Voyage model, combine your own calm-water model with Optimum Voyage weather-impact modelling, or use a complete external model.

Can different vessels use different models?

Yes. The modelling setup can be adapted vessel by vessel, allowing different vessel classes, fleets and customer requirements to be supported.

How are completed results delivered?

Your system receives a webhook notification when an optimization result is ready and then retrieves the structured result through the API.

Can voyages be updated after departure?

Yes. Voyages can be re-optimized as the vessel progresses and updated forecasts or operational requirements become available, daily until arrival.

Can the route be used onboard?

An ECDIS-compatible RTZ route is returned with the optimization result, supporting the transfer of the recommended route into onboard navigation workflows.

Can the service be white-labelled?

Yes. Optimization results can be presented inside your own platform and customer experience. Partner-branded reporting can also be supported.

Do we need to automate everything from day one?

No. Voyages and results can initially be handled through a combination of API delivery, portal access, reports, email and operational support while the complete integration is being developed.

Is technical documentation available?

Yes. Complete technical documentation, authentication information and implementation support are provided as part of the integration and onboarding process.