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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
MarineTraffic

MarineTraffic Vessel Positions (Legacy API) API

The Vessel Positions (Legacy API) API from MarineTraffic — 7 operation(s) for vessel positions (legacy api).

Documentation Provider Profile APIs.io OpenAPI GitHub

MarineTraffic Vessel Positions (Legacy API) 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 Vessel Positions (Legacy API). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 5 JSON Schemas.

This API exposes 7 operations across 7 paths, and defines 23 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.

7 operations 7 paths 23 schemas 7 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
Contact
MarineTraffic
Resource Areas
1

Paths & Operations 7

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

Vessel Positions (Legacy API) 7
GET
/exportvessels/{api_key}
Vessel Positions of a Static Fleet
exportvessels 6 params → 200403
GET
/exportvessels/{api_key}
Vessel Positions of a Dynamic Fleet
exportvessels__ 6 params → 200429
GET
/exportvessels/{api_key}
Vessel Positions Within a Port
exportvessels___ 6 params → 200429
GET
/exportvessels/{api_key}
Vessel Positions in a Predefined Bounding Box
exportvessels____ 6 params → 200429
GET
/exportvessels/{api_key}
Vessel Positions in a Dynamic Bounding Box
exportvessels_____ 10 params → 200429
GET
/exportvessel/{api_key}
Single Vessel Positions
exportvessel 8 params → 200400429
GET
/exportvessels-custom-area/{api_key}
Vessel Positions in a Custom Area
exportvessels-custom-area 7 params → 200429

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are 403_ps02_infinite_timespan (1 property), 429_too_many_requests (1 property), 400_ps07__missing_ship_identifier (1 property). Each schema is shown below with its type and property counts.

200_ps08_default
array
200_ps05_full
array
400_ps07__missing_ship_identifier
object
1 property
200_ps06_default
array
200_ps02_full
array
200_ps02_extended
array
200_ps03_default
array
200_ps03_full
array
200_ps06_extended
array
200_ps07_default
array
200_ps07_extended
array
429_too_many_requests
object
1 property
200_ps08_extended
array
200_ps06_full
array
200_ps04_default
array
200_ps05_default
array
200_ps02_default
array
200_ps03_extended
array
200_ps05_extended
array
403_ps02_infinite_timespan
object
1 property
200_ps04_extended
array
200_ps04_full
array
200_ps08_full
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

marine-traffic-vessel-positions-legacy-api-api-openapi.yml Raw ↑

Other APIs MarineTraffic publishes across the network.

MarineTraffic AIS API API
AE Profile APIs.io
MarineTraffic Balances API
AE Profile APIs.io
MarineTraffic Fleets API
AE Profile APIs.io
MarineTraffic Passage Plans API
AE Profile APIs.io
MarineTraffic Port Events API
AE Profile APIs.io
MarineTraffic Ports Information API
AE Profile APIs.io
MarineTraffic Reverse Geocoding API
AE Profile APIs.io
MarineTraffic Routing Information API
AE Profile APIs.io
MarineTraffic Search Vessel API
AE Profile APIs.io
MarineTraffic Single Vessel Events API
AE Profile APIs.io
MarineTraffic Vessel Historical Track API
AE Profile APIs.io
MarineTraffic Vessel Information API
AE Profile APIs.io
#Vessel Positions (Legacy API)
← Back to M APIs
API Details
ID
marine-traffic:marine-traffic-vessel-positions-legacy-api-api
Server
https://services.marinetraffic.com/api
Docs
https://servicedocs.marinetraffic.com/
Provider
MarineTraffic
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=marine-traffic-vessel-positions-legacy-api-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/marine-traffic-vessel-positions-legacy-api-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of MarineTraffic Vessel Positions (Legacy API) 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.