Modern maritime applications need more than a vessel’s latest coordinates. Fleet operators, logistics platforms, ports, researchers, and risk teams often need to understand where a vessel is, where it has been, which port it is approaching, when it may arrive, and what conditions it could encounter along the way.
The ShipFinder API brings these capabilities together through a unified maritime data platform. It provides access to global AIS positions, vessel information, historical activity, port intelligence, route and ETA predictions, marine weather, and event-based notifications.
This article provides an overview of the available datasets and the types of applications developers can build with them.
Why maritime data is challenging
AIS data contains dynamic vessel information such as position, speed, course, heading, and navigational status. It can also include static and voyage-related information such as vessel name, MMSI, IMO number, dimensions, destination, and ETA.
Working with AIS data directly presents several challenges:
- Position reports may come from terrestrial or satellite receivers.
- Reporting frequency varies by vessel, location, and AIS transmission conditions.
- Static fields may be incomplete or entered inconsistently.
- Raw positions must be connected with ports, voyages, weather, and historical activity.
- Applications may need event notifications rather than repeated API polling. ShipFinder organizes maritime information into seven core datasets, allowing developers to retrieve the information needed for a particular workflow without building every data-processing layer independently.
1. Real-time vessel positioning
The AIS dataset provides access to the latest available vessel positions and identity information.
Developers can:
- Retrieve a vessel’s latest position using its IMO number, MMSI, or name
- Search by vessel name, call sign, IMO, or MMSI
- Find vessels near a geographic coordinate
- Identify vessels inside a custom polygon
- Retrieve vessel registration, flag, and identity information These endpoints can support live vessel maps, fleet dashboards, traffic-monitoring tools, and location-based maritime applications. A fleet-management application, for example, could request the latest positions of monitored vessels and display their speed, course, heading, navigational status, and reporting timestamps on a map.
2. Port and voyage intelligence
A vessel position becomes more useful when it is connected with port activity.
The voyage dataset provides:
- Port details, coordinates, time zones, and UN/LOCODE information
- Lists of vessels currently berthed at a port
- Lists of vessels within port anchorage areas
- Inbound vessels and expected arrivals
- Predicted ETA and last reported position information These capabilities can be used to build port-awareness dashboards, arrival-monitoring systems, berth-planning tools, and logistics visibility platforms. Instead of showing only that a vessel is approaching a coastline, an application can connect the movement with an expected port arrival and the vessel’s current operational status.
3. Historical vessel activity
Historical data helps developers move from live tracking to behavior analysis.
The ShipFinder history dataset includes:
- Vessel position history for a selected period
- Historical ship-to-ship events
- Vessel port-call history
- Calls made by a vessel at a particular port
- Current port-call information
- Arrival and departure records for a selected port Historical tracks can support voyage replay, incident review, trade-flow research, performance analysis, and compliance investigations. Port-call data also provides a structured alternative to inferring every arrival or departure from raw AIS positions.
4. Route planning and ETA prediction
Maritime routes cannot be calculated reliably by drawing a straight line between two coordinates. A useful route must account for navigable waters, traffic lanes, pilot stations, and normal port approaches.
ShipFinder’s prediction dataset supports:
- Point-to-point maritime route planning
- Port-to-port route planning
- Predicted arrival times based on vessel and voyage parameters These services can be integrated into logistics platforms, voyage-planning tools, customer-facing shipment dashboards, and arrival-notification systems. Dynamic ETA information is especially useful because an arrival estimate may change as the vessel progresses through its voyage.
5. Marine weather and environmental data
Weather and ocean conditions directly affect route selection, voyage duration, safety, and port operations.
The meteorology dataset provides access to:
- Active tropical cyclone tracks
- Wind radii and forecast cones
- Port tide predictions
- Wind, wave, current, and visibility information for selected coordinates Combining vessel positions with environmental data enables developers to build weather-aware tracking interfaces and operational-risk dashboards without maintaining separate data integrations for every maritime condition.
6. Navigational warnings for Chinese waters
For applications operating along the Chinese coastline, ShipFinder provides a specialized navigational-warning dataset.
It includes official information about:
- Navigational hazards
- Restricted or affected waters
- Maritime safety alerts
- Coastal safety broadcasts This dataset can support regional voyage monitoring, safety management, and route-risk assessment.
7. Event-driven maritime applications
Not every application should repeatedly request the latest data. In many cases, the system only needs to respond when something important happens.
ShipFinder’s event services support notifications for:
- Vessel entries into or exits from geofenced areas
- Vessel speed changes beyond configured thresholds
- Position updates for monitored vessels
- Port arrivals and departures
- Dynamic ETA changes
- AIS signal loss
- Ship-to-ship activity Developers can also create and manage monitored-vessel lists. This event-driven approach is useful for alerting systems, fleet operations, workflow automation, and applications that need to react quickly while reducing unnecessary polling.
What can developers build?
By combining the available datasets, developers can create applications such as:
- Global vessel-tracking dashboards
- Fleet and watchlist monitoring systems
- Port congestion and arrival dashboards
- Historical voyage-replay tools
- Route-planning and ETA services
- Marine weather monitoring interfaces
- Geofence and vessel-speed alert systems
- AIS signal-loss detection tools
- Ship-to-ship activity monitoring
- Shipping, trade, and logistics analytics platforms A typical application might use the AIS dataset to locate a vessel, the history dataset to retrieve its previous track, the voyage dataset to understand its port activity, the prediction dataset to estimate arrival, and the event dataset to notify users when the vessel reaches its destination.
Getting started
ShipFinder provides REST-based services with JSON responses, along with push services for supported real-time positions and maritime events.
A typical integration process includes:
- Create an account and obtain the required API credentials.
- Select the dataset that matches the application’s use case.
- Review the endpoint parameters and response schema.
- Test requests with vessel identifiers such as IMO or MMSI.
- Store reporting timestamps together with vessel positions.
- Add retry, rate-limit, and missing-data handling.
- Use push events when continuous polling is unnecessary. The complete endpoint reference, request parameters, and response models are available in the official ShipFinder API documentation.
Practical integration considerations
When building with maritime data, developers should keep several points in mind.
First, always retain the AIS reporting timestamp. The time at which an API returns a record is not necessarily the time at which the vessel transmitted its position.
Second, applications should expect variable reporting intervals. Satellite availability, terrestrial receiver coverage, vessel density, transponder class, and transmission status can affect how frequently positions are received.
Third, IMO and MMSI serve different purposes. An IMO number generally remains associated with the vessel, while an MMSI is connected with its radio identity and may change under certain circumstances.
Finally, distinguish AIS-reported information from predicted or normalized information in the user interface. This helps users understand whether a destination or ETA came directly from the vessel or from an analytical model.
Conclusion
Building a useful maritime application requires more than plotting vessel markers on a map. Developers need to connect positions with vessel identities, voyages, ports, historical behavior, environmental conditions, predictions, and operational events.
ShipFinder provides these capabilities through a unified set of maritime datasets, making it possible to build applications ranging from simple vessel lookup tools to event-driven fleet and logistics platforms.
To explore the available services, visit the ShipFinder maritime data platform or review the API documentation.
