Vessel Data API Integration: MANTRAZ Data in Your Own Systems

MANTRAZ does not have to be the only system holding your vessel data. Vessel data API integration lets the readings MANTRAZ collects flow out to the systems your company already runs, through an HTTPS API rather than a manual export.

What vessel data API integration covers

• HTTPS API access to vessel data, with a service account per integration
• data delivered as JSON, described by a data dictionary so the other side knows what each field means
• pull or push, depending on how the receiving system works
• asset-based access, so an integration only sees the vessels it is meant to see
• an end-to-end integration test before it goes live

Living alongside your other systems

A fleet management system, an ERP, a command center or another internal application does not need to be replaced for MANTRAZ to add vessel data to it. MANTRAZ can act as a system of insight — the source your team goes to for what is happening on the vessel — without being forced into the role of the company's single system of record for everything.

Built to fit the vessel, not the other way around

No two fleets need the same integration. Engine count, fuel return lines, tank layout, existing sensors, the communication path available and the data a receiving system expects can all differ from one vessel to the next. That is why MANTRAZ is treated as a platform with system integration capability, and custom IoT setups are built to match what a vessel actually has, rather than fitting every vessel to one fixed configuration.

This is the same custom IoT and integration approach behind MANTRAZ more broadly — it treats a fleet where every vessel's setup differs as the normal case, not an exception the API integration has to work around.

Who uses it

IT and technical teams on the receiving side use the API, service account and data dictionary to bring vessel data into their own systems. Fleet managers and office teams keep using MANTRAZ directly for the same data, alongside whatever other system it now also reaches. Engineering teams work out what a specific vessel needs before an integration is built.

Connecting it to your systems

Every integration starts with looking at what your existing system needs and what a vessel can provide. To talk through a vessel data API integration for your fleet, contact the team.