The key changes for Ship Insight from SVMP—such as updated features, modified field names, and improvements in the API structure—are outlined below. Step-by-step guidance on the required technical adjustments and testing procedures is also provided to support a smooth transition.
Improvements
1. UI/UX Enhancements
•
When using the SaaS service, the entire list of vessels registered in the workspace can be viewed at a glance.
•
To ensure SVMP users maintain the same experience as before, the UI has been standardized based on SVMP.
2. Ship Name Labels
•
Vessel icons on the map now include ship names, making identification easier at a glance.
3. Map Zoom by Vessel Location
•
When you click on a menu, the map automatically centers and zooms to display the locations of all vessels included in that menu.
4. Fleet API Enhancements
•
Added a new API dedicated to retrieving only vessel specifications and PTA (Predicted Time of Arrival).
•
Introduced an API for accessing AIS data only, enabling faster and more efficient queries.
•
Improved vessel registration in the Fleet menu: in addition to single-vessel registration, bulk registration is now supported.
•
Enhanced single vessel query: vessel information can now be retrieved immediately without prior registration.
(Bulk queries remain available only for vessels that have already been registered.)
5. Carrier Vessel Schedule API
•
Retrieve the carrier schedule of a container vessel using its IMO number.
•
Enables quick access to schedule changes, delays, or updated port call sequences.
6. Performance Improvements
•
Overall system speed has been optimized, resulting in shorter loading times.
7. Mailing Service
•
Automatic notifications are sent when incidents related to vessels, cargo, or ports may impact delivery.
•
Each notification includes detailed incident information, helping detect potential disruptions early and enabling rapid follow-up actions to minimize further impact.
Changes
•
The ‘My Fleet’ feature in SVMP has been renamed to ‘Favorite’ in SeaVantage Insight.
•
The Company Filter has been restructured into Fleet, allowing more efficient management of vessels within the workspace.
•
In SVMP, My Fleet was available only for API accounts. In SeaVantage Insight, please use the Fleet function to register vessels.
1. API URL Update
API | SVMP | SeaVantage Insight |
[GET] /ship/search | https://svmp.seavantage.com/api/v1/ship/search | https://insight.seavantage.com/api/ship/search |
[GET] /fleet/snapshot | https://svmp.seavantage.com/api/v1/ship/snapshot | https://insight.seavantage.com/api/fleet/snapshot |
[GET] /fleet | https://svmp.seavantage.com/api/v1/company/custom/filter/ship/menulist | https://insight.seavantage.com/api/fleet |
[DELET] /fleet | https://svmp.seavantage.com/api/v1/company/custom/filter/ship/mapper/delete | https://insight.seavantage.com/api/fleet |
[POST] /fleet | https://svmp.seavantage.com/api/v1/company/custom/filter/save | https://insight.seavantage.com/api/fleet |
[GET] /fleet/categories | https://svmp.seavantage.com/api/v1/company/custom/filter
파라미터: menuType값 S 입력 | https://insight.seavantage.com/api/fleet/categories |
[GET] /port-call/{shipId} | https://svmp.seavantage.com/api/v1/ship/{shipId}/portCall | https://insight.seavantage.com/api/port-call/{shipId} |
[GET] /ship/past-track | https://svmp.seavantage.com/api/v1/ship/{shipId}/pastTrack | https://insight.seavantage.com/api/ship/past-track |
[GET] /ship/past-track/from-last-port | https://svmp.seavantage.com/api/v1/ship/{shipId}/pastTrack/fromLastPort | https://insight.seavantage.com/api/ship/past-track/from-last-port |
2. New API
API | SeaVantage Insight | Description |
[DELETE] /ship | https://insight.seavantage.com/api/ship | Deletes vessels currently in use within the workspace.
(This action removes the vessel from all accounts, regardless of whether it is registered/unregistered in Favorites or other menus.) |
[GET] /fleet/info | https://insight.seavantage.com/api/fleet/info | Retrieves vessel specifications and PTA (Predicted Time of Arrival). |
[GET] /voyage/schedule | https://insight.seavantage.com/api/voyage/schedule | Retrieves vessel schedule information. |
3. New Fields Added & Field Name Updates
•
Several field names have been revised to enhance clarity and precision.
•
Response structures have been streamlined in line with API functionality, resulting in the removal of certain fields.
•
Additional fields have been introduced to improve the accuracy of destination prediction.
•
Please refer to the Field Additions section below for further details.
3-1. [GET] /ship/search API Field Additions and Name Updates
response Object Field Changes
SVMP | SeaVantage Insight | Changes |
shipAliasName | Field name removed | |
shipTypeCargo | Field name removed | |
shipImage | Field name removed | |
hullType | Field name removed | |
gt | Field name removed | |
destination | Field name removed | |
eta | Field name removed | |
shipStatusType | Field name removed | |
builtBy | Field name removed | |
builtAt | Field name removed | |
loa | Field name removed | |
depth | Field name removed | |
maxDraught | Field name removed | |
engineBuiltBy | Field name removed | |
designedBy | Field name removed | |
serviceSpeed | Field name removed | |
useYn | Field name removed |
position Object Field Changes
•
The response structure has been streamlined in accordance with the API’s intended purpose, with redundant fields removed to ensure clarity and efficiency.
3-2. [GET] /fleet/snapshot Field Additions and Renaming
response Object Field Changes
SVMP | SeaVantage Insight | Changes |
imoNo | Field name removed | |
mmsi | Field name removed | |
callSign | Field name removed | |
shipName | Field name removed | |
shipAliasName | Field name removed | |
shipType | Field name removed | |
shipTypeBySize | Field name removed | |
shipTypeCargo | Field name removed | |
shipImage | Field name removed | |
built | Field name removed | |
dwt | Field name removed | |
hullType | Field name removed | |
gt | Field name removed | |
destination | Field name removed | |
eta | Field name removed | |
shipStatusType | Field name removed | |
builtBy | Field name removed | |
builtAt | Field name removed | |
loa | Field name removed | |
depth | Field name removed | |
maxDraught | Field name removed | |
engineBuiltBy | Field name removed | |
designedBy | Field name removed | |
serviceSpeed | Field name removed | |
nationCode | Field name removed | |
useYn | Field name removed | |
breadth | Field name removed | |
teuCapacity | Field name removed | |
liquidCapacity | Field name removed |
position Object Field Changes
SVMP | SeaVantage Insight | Changes |
callsSign | callSign | Field name updated |
siteShip Object Field Changes
•
Removed all unnecessary fields.
3-3. [GET] /fleet API Field Additions and Renaming
response Object Field Changes
SVMP | SeaVantage Insight | Changes |
deleteEnable | Field name removed | |
categoryIds | Field added for menu-based management |
ship Object Field Changes
SVMP | SeaVantage Insight | Changes |
shipImage | Field name removed | |
destination | destinationUnlocode | Field name updated |
eta | pta | Field name updated |
shipStatusType | Field name removed | |
useYn | Field name removed | |
destinationPortId | Field added for destination prediction | |
ptb | Field added for destination prediction | |
destinationTerminalName | Field added for destination prediction | |
destinationPortName | Field added for destination prediction |
position Object Field Changes
SVMP | SeaVantage Insight | Changes |
callsSign | callSign | Field name updated |
siteShip Object Field Changes
•
The response structure has been streamlined in accordance with the API’s intended purpose, with redundant fields removed to ensure clarity and efficiency.
3-4. [DELETE] /fleet API Field Additions and Renaming
Response Information Changes
•
On Success
◦
Previously, the API returned all registered vessel data except for the deleted vessel in SVMP. It has now been updated to return only HTTP Status: 204 No Content, with no Response Body provided.
•
On Failure
SVMP | SeaVantage Insight | Changes |
error_message | Field name removed | |
response | Field name added
(The structure and format of these new fields follow the same pattern as in the successful response.) |
3-5. [POST] /fleet API Field Additions and Renaming
Response Information Changes
•
On Success
◦
Previously, the API returned all registered vessel data except for the deleted vessel in SVMP. It has now been updated to return only HTTP Status: 204 No Content, with no Response Body provided.
•
On Failure
SVMP | SeaVantage Insight | Changes |
error_message | Field name removed | |
response | Field name added
(The structure and format of these new fields follow the same pattern as in the successful response.) |
3-6. [GET] /fleet/categories API Field Additions and Renaming
response Object Field Changes
SVMP | SeaVantage Insight | Changes |
menuId | Field name removed | |
parentId | Field name removed | |
menuName | Field name removed | |
menuLevel | Field name removed | |
updtDt | Field name removed | |
updusrId | Field name removed | |
registDt | Field name removed | |
registerId | Field name removed | |
staticLevel | Field name removed | |
sortSn | Field name removed | |
menuType | Field name removed | |
fleetCategoryId | Field name added | |
categoryName | Field name added | |
parentCategoryName | Field name added | |
includeShipsCount | Field name added |
3-7. [GET] /port-call/{shipId} API Field Additions and Renaming
ship Object Field Changes
•
The response structure has been streamlined in accordance with the API’s intended purpose, with redundant fields removed to ensure clarity and efficiency.
portCalls Object Field Changes
SVMP | SeaVantage Insight | Changes |
arrivalAnchId | Field name removed | |
arrivalBerthId | Field name removed |
departurePort, arrivalPort Object Field Changes
SVMP | SeaVantage Insight | Changes |
portAlias | Field name removed | |
geoData | Field name removed | |
useYn | Field name removed | |
usePortInsight | Field name removed | |
portShipType | Field name removed |
3-8. [GET] /ship/past-track API Field Additions and Renaming
ship Object Field Changes
•
The response structure has been streamlined in accordance with the API’s intended purpose, with redundant fields removed to ensure clarity and efficiency.
trackData Object Field Changes
SVMP | SeaVantage Insight | Changes |
callsSign | callSign | Field name updated |
3-9. [GET] /ship/past-track/from-last-port API Field Additions and Renaming
ship Object Field Changes
•
The response structure has been streamlined in accordance with the API’s intended purpose, with redundant fields removed to ensure clarity and efficiency.
trackData Object Field Changes
SVMP | SeaVantage Insight | Changes |
callsSign | callSign | Field name updated |
SVMP Data Migration
The data migration process typically takes about 30 minutes. To ensure a smooth transition, please coordinate your available time in advance. For scheduling and further arrangements, kindly contact us at sales@seavantage.com.