Voyage Information

Single Vessel Voyage Forecast

Get voyage information for a single vessel.

Notes

  • Information about AIS-transmitted data
  • SPEED returned in (knots x10) and TIMESTAMP in UTC
  • The frequency of allowed API calls is specific to your API key and is detailed in your contract as a number of successful calls per time period. For example “2 calls per minute”.
    Regardless of this agreed limit, each API key is technically restricted to a maximum of 100 total (including successful and unsuccessful) requests per minute to ensure system stability.
path Parameters
api_key
required
string

API key: 40-character hexadecimal number

query Parameters
v
required
integer
Default: 1

Version of the service to be executed. Use version 2 to get the latest

mmsi
required
integer

The Maritime Mobile Service Identity (MMSI) of the vessel you wish to track

You can instead use imo or shipid

imo
integer

The International Maritime Organization (IMO) number of the vessel you wish to track

shipid
integer

A uniquely assigned ID by MarineTraffic for the subject vessel

msgtype
string
Default: "simple"

Resolution of the response. Available values:

  • simple
  • extended
If used with the value extended, the response includes voyage related information (eg. distance travelled and to-go, load condition) and the estimated route to the vessel's destination
protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • jsono

Responses

Response samples

Content type
Example
[
  • {
    }
]

Fleet Voyage Forecast

Get voyage information for one for your MarineTraffic Fleets.

Notes

  • Information about AIS-transmitted data
  • SPEED returned in (knots x10) and TIMESTAMP in UTC
  • The frequency of allowed API calls is specific to your API key and is detailed in your contract as a number of successful calls per time period. For example “2 calls per minute”.
    Regardless of this agreed limit, each API key is technically restricted to a maximum of 100 total (including successful and unsuccessful) requests per minute to ensure system stability.
path Parameters
api_key
required
string

API key: 40-character hexadecimal number

query Parameters
v
required
integer
Default: 1

Version of the service to be executed. Use version 2 to get the latest

fleet_id
required
integer

The fleet id you wish to receive voyage forecast for

msgtype
string
Default: "simple"

Resolution of the response. Available values:

  • simple
  • extended
If used with the value extended, the response includes voyage related information (eg. distance travelled and to-go, load condition) and the estimated route to the vessel's destination
protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • jsono

Responses

Response samples

Content type
Example
[
  • {
    }
]

Single Vessel Predictive Destinations

Receive a prediction of the likely destination of a single vessel.

Notes

  • The frequency of allowed API calls is specific to your API key and is detailed in your contract as a number of successful calls per time period. For example “2 calls per minute”.
    Regardless of this agreed limit, each API key is technically restricted to a maximum of 100 total (including successful and unsuccessful) requests per minute to ensure system stability.
path Parameters
api_key
required
string

API key: 40-character hexadecimal number

query Parameters
mmsi
required
integer

The Maritime Mobile Service Identity (MMSI) of the vessel you wish to track

You can instead use imo or shipid

imo
integer

The International Maritime Organization (IMO) number of the vessel you wish to track

shipid
integer

A uniquely assigned ID by MarineTraffic for the subject vessel

fromportid
integer

The MarineTraffic ID of the port you wish to receive a prediction (found on the URL of the respective Port page)

protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • json
  • jsono

Responses

Response samples

Content type
[
  • {
    }
]

Fleet Predictive Destinations

Receive a prediction of the likely destination for one of your MarineTraffic fleets.

Notes

  • The frequency of allowed API calls is specific to your API key and is detailed in your contract as a number of successful calls per time period. For example “2 calls per minute”.
    Regardless of this agreed limit, each API key is technically restricted to a maximum of 100 total (including successful and unsuccessful) requests per minute to ensure system stability.
path Parameters
api_key
required
string

API key: 40-character hexadecimal number

query Parameters
fleet_id
required
integer

The MarineTraffic ID of the fleet you wish to track

fromportid
integer

The MarineTraffic ID of the port you wish to receive a prediction (found on the URL of the respective Port page)

protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • json
  • jsono

Responses

Response samples

Content type
[
  • {
    }
]

Vessel ETA to Port

Get ETA and voyage information for a vessel of your choice, to any port you define.

Notes

  • The frequency of allowed API calls is specific to your API key and is detailed in your contract as a number of successful calls per time period. For example “2 calls per minute”.
    Regardless of this agreed limit, each API key is technically restricted to a maximum of 100 total (including successful and unsuccessful) requests per minute to ensure system stability.
path Parameters
api_key
required
string

API key: 40-character hexadecimal number

query Parameters
v
required
integer
Default: 1

Version of the service to be executed. Use version 2 to get the latest

portid
required
integer

The MarineTraffic ID of the port you wish to receive ETA info

You can instead use unlocode

unlocode
string

The UN LOCODE (without gaps or spaces) of the port you wish to receive ETA info

mmsi
required
integer

The Maritime Mobile Service Identity (MMSI) of the vessel you wish to track

You can instead use imo or shipid

imo
integer

The International Maritime Organization (IMO) number of the vessel you wish to track

shipid
integer

A uniquely assigned ID by MarineTraffic for the subject vessel

speed_calc
integer

The Speed of the Vessel that MarineTraffic will use to produce the ETA value

  • f not defined the last average speed of the Vessel will be used
  • if no average speed exists then a default value of 12(kn) will be used
msgtype
string
Default: "simple"

Resolution of the response. Available values:

  • simple
  • extended
If used with the value extended, the response includes voyage related data
protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • json
  • jsono

Responses

Response samples

Content type
Example
[
  • {
    }
]
➔ Next to Ports Information