How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

MarineTraffic Fleets API

The Fleets API from MarineTraffic — 4 operation(s) for fleets.

MarineTraffic Fleets API is one of 14 APIs that MarineTraffic publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 5 JSON Schema definitions.

Tagged areas include Fleets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 5 JSON Schemas.

This API exposes 4 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.0.2, at version 1.0.0.

Requests are made against a single base URL, https://services.marinetraffic.com/api.

4 operations 4 paths 11 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
1.0.0
Server
https://services.marinetraffic.com/api
Resource Areas
1

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

Fleets 4
GET
/setfleet/{api_key}
Modify Fleet
setfleet 7 params → 200400404429
GET
/getfleet/{api_key}
Vessels in Fleet
getfleet 5 params → 200400403429
GET
/getfleets/{api_key}
List Fleets
getfleets 2 params → 200429
GET
/clearfleet/{api_key}
Clear Fleet
clearfleet 2 params → 200404429

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are 400_pu02_empty_fleet (1 property), 400_pu01_invalid_ship_identifier (1 property), 404_pu01_invalid_fleet_identifier (1 property), 200_pu01_update (1 property). Each schema is shown below with its type and property counts.

200_pu01_update
object
1 property
200_pu02_default
array
200_pu05_default
array
400_pu01_invalid_ship_identifier
object
1 property
400_pu02_empty_fleet
object
1 property
429_too_many_requests
object
1 property
400_pu01_missing_ship_identifier
object
1 property
200_pu03_default
array
404_pu05_missing_or_invalid_fleet_identifier
object
1 property
403_pu02_invalid_fleet_identifier
object
1 property
404_pu01_invalid_fleet_identifier
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

marine-traffic-fleets-api-openapi.yml Raw ↑

Other APIs MarineTraffic publishes across the network.

MarineTraffic AIS API API
MarineTraffic Balances API
MarineTraffic Passage Plans API
MarineTraffic Port Events API
MarineTraffic Ports Information API
MarineTraffic Reverse Geocoding API
MarineTraffic Routing Information API
MarineTraffic Search Vessel API
MarineTraffic Single Vessel Events API
MarineTraffic Vessel Historical Track API
MarineTraffic Vessel Information API
MarineTraffic Vessel Positions (Legacy API) API
Where this information came from

This is an independent, third-party profile of MarineTraffic Fleets API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.