openapi: 3.0.2 info: title: MarineTraffic Events AIS API Routing 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: Routing Information paths: /exportroutes/{api_key}: get: tags: - Routing Information summary: Vessel Route to Port description: "A newer version of this endpoint is available here: https://developers.kpler.com/spec/c78f79cf-4169-4a59-987d-e5970ea170f9

\nReceive a list of available routes and distances from a vessel to a port.

Notes " operationId: exportroutes parameters: - $ref: '#/components/parameters/api_key' - $ref: '#/components/parameters/mmsi_VI03' - $ref: '#/components/parameters/imo_VI03' - $ref: '#/components/parameters/shipid_VI03' - $ref: '#/components/parameters/port_target_id_VI03' - $ref: '#/components/parameters/includealternatives_VI03' - $ref: '#/components/parameters/includeinland_VI03' - $ref: '#/components/parameters/msgtype_VI03' - $ref: '#/components/parameters/protocol' responses: '200': description: Successful Response content: application/json: schema: oneOf: - $ref: '#/components/schemas/200_vi03_default' - $ref: '#/components/schemas/200_vi03_extended' application/xml: schema: oneOf: - $ref: '#/components/schemas/200_vi03_default' - $ref: '#/components/schemas/200_vi03_extended' examples: Default: summary: Simple value: "\n\n \n" Extended: summary: Extended value: "\n\n \n" '400': description: Bad Request content: application/json: schema: oneOf: - $ref: '#/components/schemas/400_vi03_invalid_ship_identifier' - $ref: '#/components/schemas/400_vi03_missing_or_invalid_port_identifier' application/xml: schema: oneOf: - $ref: '#/components/schemas/400_vi03_invalid_ship_identifier' - $ref: '#/components/schemas/400_vi03_missing_or_invalid_port_identifier' examples: Invalid ship identifier: summary: Invalid ship identifier value: "\n\n \n \n \n" Missing or invalid port identifier: summary: Missing or invalid port 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" '/exportroutes/{api_key} ': get: tags: - Routing Information summary: Distance to Port description: "A newer version of this endpoint is available here: https://developers.kpler.com/spec/c78f79cf-4169-4a59-987d-e5970ea170f9

\nReceive a list of available routes and distances from point or port to a specific port.

Notes " operationId: exportroutes_ parameters: - $ref: '#/components/parameters/api_key' - $ref: '#/components/parameters/port_start_id_VI03' - $ref: '#/components/parameters/LAT_VI03' - $ref: '#/components/parameters/LON_VI03' - $ref: '#/components/parameters/port_target_id_VI03' - $ref: '#/components/parameters/includealternatives_VI03' - $ref: '#/components/parameters/includeinland_VI03' - $ref: '#/components/parameters/msgtype_VI03' - $ref: '#/components/parameters/protocol' responses: '200': description: Successful Response content: application/json: schema: oneOf: - $ref: '#/components/schemas/200_vi03_default' - $ref: '#/components/schemas/200_vi03_extended' application/xml: schema: oneOf: - $ref: '#/components/schemas/200_vi03_default' - $ref: '#/components/schemas/200_vi03_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_vi03_missing_or_invalid_port_identifier' application/xml: schema: $ref: '#/components/schemas/400_vi03_missing_or_invalid_port_identifier' examples: Missing or invalid port identifier: summary: Missing or invalid port 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: mmsi_VI03: name: mmsi in: query description: The Maritime Mobile Service Identity (MMSI) of the vessel you wish to track

You can instead use imo or shipid required: true schema: type: integer LAT_VI03: name: LAT in: query description: The latitude of the starting point

It can be used together with LON instead of port_start_id required: false schema: type: number shipid_VI03: name: shipid in: query description: A uniquely assigned ID by MarineTraffic for the subject vessel required: false schema: type: integer msgtype_VI03: name: msgtype in: query description: "Resolution of the response. Available values: If used with the value extended, the response includes also route/waypoints as Linestring Geometry in WKT - Well-Known Text" required: false schema: type: string default: simple includealternatives_VI03: name: includealternatives in: query description: Use 1 to search for all available routes regarding the specific journey or 0 to not include alternative routes required: false schema: type: integer includeinland_VI03: name: includeinland in: query description: Use 1 in order to receive routes which include inland waterways or 0 to not include alternative routes required: false schema: type: integer protocol: name: protocol in: query description: "Response type. Use one of the following: