openapi: 3.0.2 info: title: MarineTraffic Events AIS API Vessel Information API version: 1.0.0 description: Port calls, berth calls, and event timelines for single vessels and entire ports — surfacing every arrival, departure, and berth touch detected by the global AIS network. contact: name: MarineTraffic url: https://www.marinetraffic.com/ servers: - url: https://services.marinetraffic.com/api tags: - name: Vessel Information paths: /exportvesselphoto/{api_key}: get: tags: - Vessel Information summary: Vessel Photo description: "Retrieve the most popular photo of a 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.

" operationId: exportvesselphoto parameters: - $ref: '#/components/parameters/api_key' - $ref: '#/components/parameters/vessel_id_VD01' - $ref: '#/components/parameters/shipid_VD01' - $ref: '#/components/parameters/protocol' responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/200_vd01_default' application/xml: schema: $ref: '#/components/schemas/200_vd01_default' examples: Default: summary: Simple value: "\n\n \n" '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/400_vd01_missing_or_invalid_ship_identifier' application/xml: schema: $ref: '#/components/schemas/400_vd01_missing_or_invalid_ship_identifier' examples: Missing or invalid ship identifier: summary: Missing or invalid ship identifier value: "\n\n \n \n \n" '429': description: Too Many Requests content: application/json: schema: $ref: '#/components/schemas/429_too_many_requests' application/xml: schema: $ref: '#/components/schemas/429_too_many_requests' examples: Area out of bound: summary: Too Many Requests value: "\n\n \n \n \n" /vesselmasterdata/{api_key}: get: tags: - Vessel Information summary: Vessel Particulars (Legacy API) description: "⚠️This is a legacy endpoint.

\nA new and improved version is now available, offering enhanced data quality, latest features and better performance. \nWe strongly recommend switching to the latest version, which you can explore here: Vessel Particulars & Ownership.

\nIf you would like to see the new endpoint in action, feel free to request a demo - our team would be happy to walk you through it.

\nRetrieve particulars for one or more vessels.

Notes

Information about AIS-transmitted data
If page parameter is missing, then default page:1 will be used instead
The results returned from the API call are split into pages of 100 rows
In order to get each page generated by the call, add the /page:#value/ parameter to the URL. The default value is /page:1/
The API does not return results for vessels that are not IMO-registered
The API does not return results for dead vessels
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.

" operationId: vesselmasterdata parameters: - $ref: '#/components/parameters/api_key' - $ref: '#/components/parameters/v_VD02' - $ref: '#/components/parameters/mmsi_VD02' - $ref: '#/components/parameters/imo_VD02' - $ref: '#/components/parameters/shipid_VD02' - $ref: '#/components/parameters/timespan_VD02' - $ref: '#/components/parameters/interval_VD02' - $ref: '#/components/parameters/protocol' - $ref: '#/components/parameters/page_VD02' - $ref: '#/components/parameters/msgtype_VD02' responses: '200': description: Successful Response content: application/json: schema: oneOf: - $ref: '#/components/schemas/200_vd02_default' - $ref: '#/components/schemas/200_vd02_extended' application/xml: schema: oneOf: - $ref: '#/components/schemas/200_vd02_default' - $ref: '#/components/schemas/200_vd02_extended' examples: Default: summary: Simple value: "\n\n \n" Extended: summary: Extended value: "\n\n \n" '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/400_vd02_missing_or_invalid_ship_identifier' application/xml: schema: $ref: '#/components/schemas/400_vd02_missing_or_invalid_ship_identifier' examples: Missing or invalid ship identifier: summary: Missing or invalid ship identifier value: "\n\n \n \n \n" '429': description: Too Many Requests content: application/json: schema: $ref: '#/components/schemas/429_too_many_requests' application/xml: schema: $ref: '#/components/schemas/429_too_many_requests' examples: Area out of bound: summary: Too Many Requests value: "\n\n \n \n \n" components: parameters: timespan_VD02: name: timespan in: query description: The timespan parameter defines the period of time, during which we want to receive the change in a vessel's details

The maximum value can be either 5 when the interval parameter is set to days or 2880 when the interval is set to minutes required: false schema: type: integer mmsi_VD02: name: mmsi in: query description: The Maritime Mobile Service Identity (MMSI) of the vessel you wish to track (single or comma separated values)

You can instead use imo or shipid required: true schema: type: integer page_VD02: name: page in: query description: Page number of the results to be returned required: false schema: type: integer default: 1 msgtype_VD02: name: msgtype in: query description: "Resolution of the response. Available values:

simple
extended

" required: false schema: type: string default: simple shipid_VD02: name: shipid in: query description: A uniquely assigned ID by MarineTraffic for the subject vessel (single or comma separated values) required: false schema: type: integer api_key: name: api_key in: path description: 'API key: 40-character hexadecimal number' required: true schema: type: string protocol: name: protocol in: query description: "Response type. Use one of the following:

xml
csv
json
jsono

instead