MarineTraffic logo

Single Vessel Events

Single Vessel Port Calls

Retrieve arrival and departure information of a vessel for a specific period of time.

Notes

  • Data is available for dates after 2015-01-16
  • Information about AIS-transmitted data
  • MOVE_TYPE values: 1=Departure, 0=Arrival
  • 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 6 to get the latest

shipid
required
integer

A uniquely assigned ID by MarineTraffic for the subject vessel

You can instead use imo or mmsi

mmsi
integer

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

imo
integer

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

timespan
integer
Default: 2

The maximum age, in minutes, of the returned port calls. Maximum value is 2880

movetype
integer

Use 0 to only receive arrivals or 1 to only receive departures. If not used, the response will include both

exclude_intransit
integer

Use 1 to exclude vessels in transit

fromdate
string <date-time>

Portcalls between fromdate and todate. Maximum period requested 190 days

Date format: YYYY-MM-DD HH:MM

todate
string <date-time>

Portcalls between fromdate and todate. Maximum period requested 190 days

Date format: YYYY-MM-DD HH:MM

dwt_min
integer

Data filter: minimum DWT

Applicable to IMO-having vessels

dwt_max
integer

Data filter: maximum DWT

Applicable to IMO-having vessels

gt_min
integer

Data filter: minimum GT

Applicable to IMO-having vessels

gt_max
integer

Data filter: maximum GT

Applicable to IMO-having vessels

market
string

Define market(s) for which you would like to receive port calls (single or comma separated values) - more

msgtype
string
Default: "simple"

Resolution of the response. Available values:

  • simple
  • extended

If used with the value extended, the response includes voyage related data since the previous port call
protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • jsono

Responses

Response samples

Content type
application/json
application/json
application/xml
Example
Simple
Simple
Extended
[
  • {
    },
  • {
    }
]

Single Vessel Events

Get event based intelligence for a vessel.

Notes

  • Here is a COMPLETE LIST OF EVENT TYPES available for this endpoint. You can use these as values for the event_type query parameter.
  • Information about AIS-transmitted data
  • 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

shipid
required
integer

A uniquely assigned ID by MarineTraffic for the subject vessel

You can instead use imo or mmsi

mmsi
integer

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

imo
integer

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

timespan
integer
Default: 60

The maximum age, in minutes, of the returned port calls. Maximum value is 2880

fromdate
string <date-time>

Vessel Events between fromdate and todate

Date format: YYYY-MM-DD HH:MM:SS

todate
string <date-time>

Vessel Events between fromdate and todate

Date format: YYYY-MM-DD HH:MM:SS

event_type
integer

You may use one or more event ids in comma separated format for the events you wish to receive

limit_events
integer

Limit the number of results

protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • jsono

Responses

Response samples

Content type
application/json
application/json
application/xml
[
  • {
    },
  • {
    }
]

Single Vessel Berth Calls

Get berth arrival and departure information for a specific vessel.

Notes

  • Data is available for dates after 2017-07-03
  • Information about AIS-transmitted data
  • More information about input parameters: MARKET, SHIPCLASS
  • 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 3 to get the latest

shipid
required
integer

A uniquely assigned ID by MarineTraffic for the subject vessel

You can instead use imo or mmsi

mmsi
integer

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

imo
integer

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

timespan
integer
Default: 2

The maximum age, in minutes, of the returned port calls. Maximum value is 2880

fromdate
string <date-time>

Berth calls between fromdate and todate. Maximum period requested 15 days

Date format: YYYY-MM-DD HH:MM:SS.

todate
string <date-time>

Berth calls between fromdate and todate. Maximum period requested 15 days

Date format: YYYY-MM-DD HH:MM:SS

market
string

Define market for which you would like to receive berth calls - more

  • if undefined and ship-class is also undefined, then return all
  • if undefined and ship-class is defined, return based on ship-class
  • if defined and ship-class is undefined, return all ship-classes of the specific market

shipclass
integer

Define ship class of interest - more

dwt_min
integer

Data filter: minimum DWT

Use it to filter by size Cargo and Tanker IMO-having vessels (shiptype = 7,8)

dwt_max
integer

Data filter: maximum DWT

Use it to filter by size Cargo and Tanker IMO-having vessels (shiptype = 7,8)

gt_min
integer

Data filter: minimum GT

Applicable to IMO-having vessels

gt_max
integer

Data filter: maximum GT

Applicable to IMO-having vessels

movetype
integer

Use 0 to include both, 1 to only receive dockings or 2 for only undockings within the defined period. If not used, only dockings are returned

Available only from version 2 of the service

protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • jsono

msgtype
string
Default: "simple"

Resolution of the response. Available values:

  • simple
  • extended

If used with the value extended, the response includes voyage related data since the previous port call

Responses

Response samples

Content type
application/json
application/json
application/xml
Example
Simple
Simple
Extended
[
  • {
    },
  • {
    }
]
➔ Next to Port Events