MariTrace API

Legacy APIs

The MariTrace API, the MariData API and the PublicAPIs keep working exactly as they always have, at the same addresses and with the same sign-in. This page describes them and lets you try them.

Open the legacy reference New here? Use v1

The three APIs

MariTrace API

https://api.maritrace.com
  • Sign in: POST /registration with HTTP Basic, then send the token header
  • GET /vesselpositions: positions changed since your last call
  • /vesselpositions_subscribedvessels: list, add, remove vessels

Reference & try it

MariData API

https://api.maridata.com
  • Sign in: HTTP Basic on every call, from an IP address on your account
  • POST /api/Vessels, VesselsByName, VesselLatestPosition, SATCAIS, Countries, AreaCheck
  • JSON or XML

Reference & try it

PublicAPIs

https://apis.maritrace.com
  • Sign in: HTTP Basic on every call
  • 22 POST /get_… calls: vessels, positions, areas, ports, port calls, JWC

Reference & try it

Trying a call

Open an API in the legacy reference, press Authorize and enter your username and password (or, for the MariTrace API, a token from /registration), then open a call and choose Try it out.

These are real calls, made from your browser to the live API. They sign in as you, come from your own IP address (MariData checks it against your account) and count towards your rate limits and any usage billing, just like calls from your systems. Your credentials stay in this browser tab.

One exception: the MariTrace API's GET /vesselpositions and the calls that add or remove subscribed vessels are previews here. You see the real answer, but your cursor does not move and your list does not change, so trying them never takes updates away from your own systems. With subscriptiontype=test and fleetname=test they return sample data.

Rate limits and errors

Limits are set per user and per API. When you reach one, the MariData API answers 429 with a message saying which limit (second, minute, hour or day). The MariTrace API and the PublicAPIs answer 401 when the sign-in or token is not accepted for that call.

Moving to v1

New integrations should use the v1 API: one key for every product, versioned paths, consistent JSON and rate-limit headers on every response. Talk to us when you want to move; the legacy APIs keep running meanwhile.