MarineTraffic logo

Ports Information

Expected Port Arrivals

Get expected arrivals to a specific port.

Notes

  • SPEED returned in (knots x10) and TIMESTAMP in UTC
  • Use either TIMESPAN or FROMDATE/TODATE in order to look for expected arrivals in a specific date range
  • 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 4 to get the latest

portid
required
integer

The MarineTraffic ID of the port (found on the URL of the respective Port page) or port UNLOCODE

timespan
integer

Number of days in the future to look for expected arrivals, starting from the time the API call is requested

Maximum value is 40 days

If neither this nor the fromdate/todate parameters are used, the response only includes vessels currently in port (or the country’s ports) and the last vessel's signal is received during the last 2 days

days_last_signal
integer

Include vessels currently in port that have transmitted a position within the last x days (based on their last signal timestamp).

This parameter only works when no other timeframe is defined.

fromdate
string <date-time>

Timestamp in the future to start looking for expected arrivals. If used, then you should also define the todate parameter

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

todate
string <date-time>

Timestamp in the future to start looking for expected arrivals. If used, then you should also define the fromdate parameter

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

fromportid
integer

The MarineTraffic ID of the previous port (found on the URL of the respective Port page) or previous port UNLOCODE

shiptype
integer

Filter data by vessel type:

  • 2: Fishing
  • 4: High Speed Craf
  • 6: Passenger
  • 7: Cargo
  • 8: Tanker

dwt_min
integer

Data filter: minimum DWT

Use it to filter by size Cargo and Tanker IMO-having vessels (shiptype = 7,8). If used, then you should also define the dwt_max parameter

dwt_max
integer

Data filter: maximum DWT

Use it to filter by size Cargo and Tanker IMO-having vessels (shiptype = 7,8). If used, then you should also define the dwt_min parameter

gt_min
integer

Data filter: minimum GT

Applicable to IMO-having vessels. If used, then you should also define the gt_max parameter

gt_max
integer

Data filter: maximum GT

Applicable to IMO-having vessels. If used, then you should also define the gt_min parameter

msgtype
string
Default: "simple"

Resolution of the response. Available values:

  • simple
  • extended

If used with the value extended, apart from the ETA information, the response includes main vessel particulars. If omitted, the returned records include only position and ETA reports
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
[
  • {
    },
  • {
    }
]

Expected Country Arrivals

Get expected arrivals to a specific country.

Notes

  • SPEED returned in (knots x10) and TIMESTAMP in UTC
  • Use either TIMESPAN or FROMDATE/TODATE in order to look for expected arrivals in a specific date range
  • 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 4 to get the latest

country
required
integer

The Country code of interest. Response includes all ports within the Country

timespan
integer

Number of days in the future to look for expected arrivals, starting from the time the API call is requested

Maximum value is 40 days

If neither this nor the fromdate/todate parameters are used, the response only includes vessels currently in port (or the country’s ports) and the last vessel's signal is received during the last 2 days

days_last_signal
integer

Include vessels currently in port that have transmitted a position within the last x days (based on their last signal timestamp).

This parameter only works when no other timeframe is defined.

fromdate
string <date-time>

Timestamp in the future to start looking for expected arrivals. If used, then you should also define the todate parameter

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

todate
string <date-time>

Timestamp in the future to start looking for expected arrivals. If used, then you should also define the fromdate parameter

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

fromportid
integer

The MarineTraffic ID of the previous port (found on the URL of the respective Port page) or previous port UNLOCODE

shiptype
integer

Filter data by vessel type:

  • 2: Fishing
  • 4: High Speed Craf
  • 6: Passenger
  • 7: Cargo
  • 8: Tanker

dwt_min
integer

Data filter: minimum DWT

Use it to filter by size Cargo and Tanker IMO-having vessels (shiptype = 7,8). If used, then you should also define the dwt_max parameter

dwt_max
integer

Data filter: maximum DWT

Use it to filter by size Cargo and Tanker IMO-having vessels (shiptype = 7,8). If used, then you should also define the dwt_min parameter

gt_min
integer

Data filter: minimum GT

Applicable to IMO-having vessels. If used, then you should also define the gt_max parameter

gt_max
integer

Data filter: maximum GT

Applicable to IMO-having vessels. If used, then you should also define the gt_min parameter

msgtype
string
Default: "simple"

Resolution of the response. Available values:

  • simple
  • extended

If used with the value extended, apart from the ETA information, the response includes main vessel particulars. If omitted, the returned records include only position and ETA reports
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
[
  • {
    },
  • {
    }
]

Predictive Port Arrivals

Receive a prediction of the vessels likely to arrive to a specific port.

Notes

  • 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
portid
required
integer

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

market
integer

Define market for which you would like to receive probable visits - 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

probability
integer

Define probability over which you would like to receive probable visits (accepted > 0.3)

protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • json
  • jsono

Responses

Response samples

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

Port Congestion

Receive the Port Congestion for a specific period of time.

Notes

  • More information about input parameters: MARKET, SHIPCLASS
  • The API charges per record are based on the parameters used. If there is a mix of parameters (simple,extended or full), then the parameter of greatest value is taken into account to calculate the API call cost
  • NOT ALLOWED combinations in request
    • agg_market:1 and agg_shipclass:0
    • agg_market:1 and agg_port:1
    • agg_shipclass:1 and agg_port:1
    • agg_market:1 and shipclass (specific value in shipclass e.g. POST PANAMAX)
  • 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
portid
integer

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

year
required
integer

Year of interest (data available back to 1 year). Information further back can be requested ad-hoc

week
required
integer

Week of Year that is of interest (e.g. for week 18/2018 input 18). For range of weeks use comma e.g. for weeks 30 to 35 (30,35)

market
integer

Define market for which you would like to receive port congestion - more

  • if undefined and ship-class is also undefined, then figures for ALL markets/ship-class
  • if undefined and ship-class is defined, returns based on ship-class for ALL applicable to size class markets
  • if defined and ship-class is undefined, returns figures for the specific market (no size class breakdown)

shipclass
integer

Define ship class of interest - more

agg_port
integer

If used, portid should not be in request

  • when agg_port = 1 is used, aggregation result of all ports are returned
  • when agg_port = 1 is used, agg_market cannot be 1

agg_market
integer

If used, market should not be in request

  • if agg_market = 1, aggregation result of all markets will be returned
  • if 0, a breakdown of markets will be returned

agg_shipclass
integer

If used, shipclass should not be in request

  • if agg_shipclass = 1, aggregation result of all classes will be returned
  • if 0, a breakdown of classes will be returned

time_anch
string

The median number of days spent at anchorage by the selected market/shipclass. Values indicate in between set to be returned

Comma separated float numbers (one decimal)

Available only if extended version of the API is used

time_port
string

The median number of days spent at port by the selected market/shipclass. Values indicate in between set to be returned

Comma separated float numbers (one decimal)

Available only if extended version of the API is used

vessels
integer

Number of vessels that were used in the median calculations. Value of parameter indicates greater than relation

Available only if extended version of the API is used

calls
integer

Number of individual calls that were used in the median calculations (e.g. if the same vessel has called twice within the same week, it will count twice in calls and once in vessels. Value of parameter indicates greater than relation

Available only if extended version of the API is used

time_anch_stdev
string

The standard deviation of days spent at anchorage the previous week. Values indicate in between set to be returned (time_anch_stdev:0.5,1.5)

Comma separated float numbers (one decimal)

Available only if full version of the API is used

time_anch_diff
string

The week-to-week difference of number of days spent at anchorage. Values indicate in between set to be returned

Comma separated float numbers (one decimal)

Available only if full version of the API is used

time_anch_diff_perc
string

The week-to-week difference of number of days spent at anchorage as a percentage. Values indicate in between set to be returned

Comma separated float numbers (one decimal)

Available only if full version of the API is used

time_port_stdev
string

The standard deviation of days spent at port the previous week. Values indicate in between set to be returned (time_port_stdev:0.5,1.5)

Comma separated float numbers (one decimal)

Available only if full version of the API is used

time_port_diff
string

The week-to-week difference of number of days spent at port. Values indicate in between set to be returned

Comma separated float numbers (one decimal)

Available only if full version of the API is used

time_port_diff_perc
string

The week-to-week difference of number of days spent at port as a percentage. Values indicate in between set to be returned

Comma separated float numbers (one decimal)

Available only if full version of the API is used

protocol
string
Default: "xml"

Response type. Use one of the following:

  • xml
  • csv
  • json
  • jsono

Responses

Response samples

Content type
application/json
application/json
application/xml
[
  • {
    }
]
➔ Next to Routing Information