/marinetraffic/vessels

POST /api/marinetraffic/vessels

Price: 1 credit

Get a MarineTraffic vessel with identity, live AIS position and current voyage by IMO or ship ID

How to use it

Get a full MarineTraffic vessel record by IMO number (7 digits) or MarineTraffic ship ID. Returns identity (IMO, MMSI, name, callsign, flag, ship type, market segment, size class, length, beam, AIS transponder class), a photo and photo count, the latest AIS position (latitude, longitude, speed, course, true heading, rate of turn, draught, navigational status, current area and report time), and the current voyage (reported destination, ETA, progress, departure and arrival port IDs, times and labels — the label marks whether each time is actual (ATD/ATA) or estimated (ETD/ETA)). Also lists maritime businesses at the arrival location. Timestamps (eta, position_received_at, departure_at, arrival_at) are unix seconds.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• vessel string required — Vessel IMO number (7 digits) or MarineTraffic ship ID (examples: "9321483", "159196"; minLength: 1)

Response

• @type string (default: "MarinetrafficVessel")
• id integer required
• name string required
• ais_name string nullable
• imo integer nullable
• eni integer nullable
• mmsi integer nullable
• callsign string nullable
• flag string nullable
• flag_code string nullable
• ship_type string nullable
• ais_type string nullable
• market string nullable
• size_class string nullable
• length_overall number nullable
• beam number nullable
• ais_transponder_class string nullable
• image string nullable
• photo_count integer nullable
• url string required
• latitude number nullable
• longitude number nullable
• speed number nullable
• course number nullable
• true_heading integer nullable
• rate_of_turn number nullable
• draught number nullable
• navigation_status string nullable
• position_received_at integer nullable
• area_name string nullable
• is_in_range boolean (default: false)
• reported_destination string nullable
• eta integer nullable
• progress number nullable
• departure_port_id integer nullable
• departure_at integer nullable
• departure_label string nullable
• arrival_port_id integer nullable
• arrival_at integer nullable
• arrival_label string nullable
• businesses array (default: [])
  • @type string (default: "MarinetrafficVesselBusiness")
  • id string required
  • name string nullable
  • activity string nullable
  • country_code string nullable
  • image string nullable
  • port_id integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Vessel not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.