MyShipTracking · Authentication Profile

Myshiptracking Authentication

Authentication

MyShipTracking secures its APIs with apiKey and http across 2 declared security schemes, as derived from its OpenAPI definitions.

Vessel TrackingAISMaritimeShip TrackingReal-Time DataShipsPort CallsMaritime DataLocationFleet Tracking

Methods: apiKey, http Schemes: 2 OAuth flows: API key in:

Security Schemes

bearerAuth http

scheme: bearer · in: header ()

x-api-key apiKey

· in: header ()

Source

Authentication Profile

generated: '2026-07-12'
method: documented
source: https://api.myshiptracking.com/ (Getting Started + per-endpoint docs)
summary:
  types:
  - apiKey
  - http
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: >-
    API key issued from your MyShipTracking account page, passed as
    `Authorization: Bearer [example key]`. Register a free account at
    MyShipTracking.com, then generate your API Key and Secret Key on the account
    page. Each user may hold one trial key (2,000 coins, 10 days).
  in: header
  sources:
  - https://api.myshiptracking.com/
  - https://api.myshiptracking.com/docs/account-info
- name: apiKeyAuth
  type: apiKey
  in: header
  name: x-api-key
  description: >-
    The same API key may instead be passed in the `x-api-key` request header.
    Either Bearer or x-api-key is accepted on every endpoint.
  sources:
  - https://api.myshiptracking.com/
  - https://api.myshiptracking.com/docs/vessel-current-position-api
notes: >-
  Authentication is required on every call. Missing keys return ERR_NO_KEY (401)
  and invalid keys return ERR_INVALID_KEY (401). Keys can be regenerated from the
  account page. The Secret Key is issued alongside the API Key at registration.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com