We’ve introduced several new features across API v2 and the Web Terminal to give you more flexibility and control when analyzing flows and vessel activity—especially in the context of recent developments in the Middle East.
🔍 What’s new
1. Transit analysis across Flows & Trades
Available on: API v2
You can now analyze data using transit movements with:
A Transit option on Flows
A Transit object on Trades
On Flows:
The flowDirection parameter now supports a new value: Transit.
This allows you to analyze flows based on movements through transit regions, in addition to existing options such as import and export.
On Trades:
A new transit object is available, returning a list of:
name (transit point)
startDate
endDate
portCallId
The portCallId allows you to directly link transit events with the Port-calls endpoint for deeper investigation.
Together, these allow you to:
Analyze flows based on transit regions, not just origin/destination
Reproduce the Transit view from Flows directly in Trades
Aggregate data using the transit start date for consistency
This is especially useful for:
Understanding flows through strategic regions
Aligning analysis between Flows and Trades datasets
2. Vessel filter on Fleet Metrics + Custom Fleets
Available on: API v2 & Web Terminal
You can now filter Fleet Metrics using specific vessels or your own custom fleets.
This is particularly useful for:
Tracking floating storage
Monitoring specific vessel groups
3. Exclude viaRoute option
Available on: API v2 & Web Terminal
You can now exclude flows that pass through intermediate routes (viaRoute).
On Web Terminal:
Use minus (-) in the via filter to exclude a location
On API v2:
Use the viaRouteExclude parameter.
This helps you:
Focus on direct flows
Remove noise from complex routing scenarios
Improve clarity in regional analysis
🌍 Why this matters
These enhancements were designed to provide greater flexibility and precision when exploring data in rapidly evolving contexts.
They allow you to:
Better track route changes and diversions
Analyze flows through key transit regions
Align datasets across endpoints for consistent insights
What Do You Think?
We’d love to hear your feedback! How does this new feature improve your workflow? Let us know your thoughts by emailing cs@kpler.com