FleetMon Fleet Tracker API
Tracking of current positions for a modifiable list of vessels.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/fleetmon-fleet-tracker-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
description: 'ARCHIVED SPECIFICATION - RETIRED API. This is the final publicly archived Swagger 2.0 definition of the FleetMon API (apiv2.fleetmon.com), preserved from the Internet Archive Wayback Machine (schema.json capture 2021-12-08; the developer portal at developer.fleetmon.com remained online through early 2025). FleetMon was acquired by Kpler in 2023, the FleetMon platform and API were phased out beginning January 2024 and migrated into MarineTraffic, and as of 2026 the fleetmon.com domain (including apiv2.fleetmon.com and developer.fleetmon.com) no longer resolves. None of the endpoints below are live. The successor surface is the MarineTraffic API portfolio / Kpler AIS (servicedocs.marinetraffic.com).
--- Original description follows ---
Welcome to our API reference!
You can view JSON response samples in the area to the right.
If you need help with the API, just [contact us](https://www.fleetmon.com/company/contact/).
Follow us on [Facebook](https://www.facebook.com/fleetmon) and [Twitter](https://twitter.com/fleetmon) for the latest updates and news on the platform.
With the use of the FleetMon API, you agree with the [Terms of Service](https://www.fleetmon.com/terms-of-service/).
'
title: FleetMon API Reference Basic Vessel Data Fleet Tracker API
version: Version 2.4.2
x-archived:
status: retired
retiredNote: FleetMon product offerings, logins, and the apiv2.fleetmon.com API were discontinued during the 2024 migration into MarineTraffic following the 2023 Kpler acquisition; fleetmon.com DNS no longer resolves as of 2026.
archiveSource: http://web.archive.org/web/20211208160310/https://apiv2.fleetmon.com/schema.json
archivedDeveloperPortal: http://web.archive.org/web/20250106234623/https://developer.fleetmon.com/reference/
successor: https://servicedocs.marinetraffic.com/
archivedBy: API Evangelist
archivedDate: '2026-07-11'
servers:
- url: https://apiv2.fleetmon.com/
tags:
- description: Tracking of current positions for a modifiable list of vessels.
name: Fleet Tracker
x-codename: fleet
x-tag-group: Professional Monitoring
paths:
/fleet/:
delete:
description: ''
operationId: delete-fleet-listing
parameters:
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: request_limit_info
required: false
schema:
type: boolean
default: false
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: size_limit_info
required: false
schema:
type: boolean
default: false
responses:
'200':
description: Fleet Tracker - clear vessels response
content:
application/json:
schema:
$ref: '#/components/schemas/fleet-response-delete'
'401':
description: The server could not verify that you are authorized to access the URL.
x-example-object:
code: 401
description: The server could not verify that you are authorized to access the URL requested.
message: Unauthorized
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-401
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'403':
description: The provided credentials were correct but the API is not yet fully configured.
x-example-object:
code: 403
description: The API is not yet fully configured.
message: Forbidden
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-403
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'405':
description: The used HTTP method is not allowed for this URL.
x-example-object:
code: 405
description: The method is not allowed for the requested URL.
message: Method Not Allowed
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-405
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'429':
description: The client requested the resource too many times. (rate limit)
x-example-object:
code: 429
description: Only 200 requests per 30 days are allowed for this endpoint.
message: Too Many Requests
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-429
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
security:
- apikey: []
- apikey_authorization_header: []
- apikey_header: []
summary: Empties the fleet completely.
tags:
- Fleet Tracker
get:
description: ''
operationId: get-fleet-listing
parameters:
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: request_limit_info
required: false
schema:
type: boolean
default: false
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: size_limit_info
required: false
schema:
type: boolean
default: false
- description: optional filter by tag name
in: query
name: tag
required: false
schema:
type: string
responses:
'200':
description: Fleet Tracker - vessels response
content:
application/json:
schema:
$ref: '#/components/schemas/fleet-response-listing'
'401':
description: The server could not verify that you are authorized to access the URL.
x-example-object:
code: 401
description: The server could not verify that you are authorized to access the URL requested.
message: Unauthorized
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-401
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'403':
description: The provided credentials were correct but the API is not yet fully configured.
x-example-object:
code: 403
description: The API is not yet fully configured.
message: Forbidden
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-403
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'405':
description: The used HTTP method is not allowed for this URL.
x-example-object:
code: 405
description: The method is not allowed for the requested URL.
message: Method Not Allowed
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-405
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'422':
description: A required parameter is missing or has a wrong structure.
x-example-object:
code: 422
description: The request was well-formed but was unable to be followed due to semantic errors.
message: Unprocessable Entity
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-422
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'429':
description: The client requested the resource too many times. (rate limit)
x-example-object:
code: 429
description: Only 200 requests per 30 days are allowed for this endpoint.
message: Too Many Requests
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-429
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
security:
- apikey: []
- apikey_authorization_header: []
- apikey_header: []
summary: Delivers the fleet.
tags:
- Fleet Tracker
post:
description: ''
operationId: post-fleet-listing
parameters:
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: request_limit_info
required: false
schema:
type: boolean
default: false
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: size_limit_info
required: false
schema:
type: boolean
default: false
responses:
'200':
description: Fleet Tracker - replace vessels response
content:
application/json:
schema:
$ref: '#/components/schemas/fleet-response-listing-replace'
'400':
description: The request body could not be parsed.
x-example-object:
code: 400
description: You sent a request that this server could not understand.
message: Bad Request
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-400
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'401':
description: The server could not verify that you are authorized to access the URL.
x-example-object:
code: 401
description: The server could not verify that you are authorized to access the URL requested.
message: Unauthorized
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-401
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'403':
description: The provided credentials were correct but the API is not yet fully configured.
x-example-object:
code: 403
description: The API is not yet fully configured.
message: Forbidden
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-403
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'405':
description: The used HTTP method is not allowed for this URL.
x-example-object:
code: 405
description: The method is not allowed for the requested URL.
message: Method Not Allowed
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-405
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'422':
description: A required parameter is missing or has a wrong structure.
x-example-object:
code: 422
description: The request was well-formed but was unable to be followed due to semantic errors.
message: Unprocessable Entity
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-422
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'429':
description: The client requested the resource too many times. (rate limit)
x-example-object:
code: 429
description: Only 200 requests per 30 days are allowed for this endpoint.
message: Too Many Requests
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-429
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
security:
- apikey: []
- apikey_authorization_header: []
- apikey_header: []
summary: Replaces the fleet with new vessels.
tags:
- Fleet Tracker
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/fleet-listing-replace'
description: Fleet Tracker - replace vessels request
required: true
put:
description: ''
operationId: put-fleet-listing
parameters:
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: request_limit_info
required: false
schema:
type: boolean
default: false
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: size_limit_info
required: false
schema:
type: boolean
default: false
responses:
'200':
description: Fleet Tracker - add vessels response
content:
application/json:
schema:
$ref: '#/components/schemas/fleet-response-listing-add'
'400':
description: The request body could not be parsed.
x-example-object:
code: 400
description: You sent a request that this server could not understand.
message: Bad Request
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-400
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'401':
description: The server could not verify that you are authorized to access the URL.
x-example-object:
code: 401
description: The server could not verify that you are authorized to access the URL requested.
message: Unauthorized
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-401
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'403':
description: The provided credentials were correct but the API is not yet fully configured.
x-example-object:
code: 403
description: The API is not yet fully configured.
message: Forbidden
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-403
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'405':
description: The used HTTP method is not allowed for this URL.
x-example-object:
code: 405
description: The method is not allowed for the requested URL.
message: Method Not Allowed
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-405
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'422':
description: A required parameter is missing or has a wrong structure.
x-example-object:
code: 422
description: The request was well-formed but was unable to be followed due to semantic errors.
message: Unprocessable Entity
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-422
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'429':
description: The client requested the resource too many times. (rate limit)
x-example-object:
code: 429
description: Only 200 requests per 30 days are allowed for this endpoint.
message: Too Many Requests
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-429
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
security:
- apikey: []
- apikey_authorization_header: []
- apikey_header: []
summary: Adds vessels to the fleet.
tags:
- Fleet Tracker
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/fleet-listing-add'
description: Fleet Tracker - add vessels request
required: true
/fleet/{vessel_id}:
delete:
description: ''
operationId: delete-fleet-detail
parameters:
- description: vessel ID
in: path
name: vessel_id
required: true
schema:
type: integer
format: int64
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: request_limit_info
required: false
schema:
type: boolean
default: false
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: size_limit_info
required: false
schema:
type: boolean
default: false
responses:
'200':
description: Fleet Tracker - remove vessel response
content:
application/json:
schema:
$ref: '#/components/schemas/fleet-response-delete'
'401':
description: The server could not verify that you are authorized to access the URL.
x-example-object:
code: 401
description: The server could not verify that you are authorized to access the URL requested.
message: Unauthorized
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-401
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'403':
description: The provided credentials were correct but the API is not yet fully configured.
x-example-object:
code: 403
description: The API is not yet fully configured.
message: Forbidden
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-403
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'404':
description: Requested item does not exist.
x-example-object:
code: 404
description: The requested item was not found on the server.
message: Not Found
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-404
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'405':
description: The used HTTP method is not allowed for this URL.
x-example-object:
code: 405
description: The method is not allowed for the requested URL.
message: Method Not Allowed
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-405
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'422':
description: A required parameter is missing or has a wrong structure.
x-example-object:
code: 422
description: The request was well-formed but was unable to be followed due to semantic errors.
message: Unprocessable Entity
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-422
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'429':
description: The client requested the resource too many times. (rate limit)
x-example-object:
code: 429
description: Only 200 requests per 30 days are allowed for this endpoint.
message: Too Many Requests
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-429
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
security:
- apikey: []
- apikey_authorization_header: []
- apikey_header: []
summary: Removes a single vessel from the fleet.
tags:
- Fleet Tracker
get:
description: ''
operationId: get-fleet-detail
parameters:
- description: vessel ID
in: path
name: vessel_id
required: true
schema:
type: integer
format: int64
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: request_limit_info
required: false
schema:
type: boolean
default: false
- description: If `true` some extra attributes will be added to the response informing about usage and limits of this endpoint.
in: query
name: size_limit_info
required: false
schema:
type: boolean
default: false
responses:
'200':
description: Fleet Tracker - vessel response
content:
application/json:
schema:
$ref: '#/components/schemas/fleet-response-vessel'
'401':
description: The server could not verify that you are authorized to access the URL.
x-example-object:
code: 401
description: The server could not verify that you are authorized to access the URL requested.
message: Unauthorized
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-401
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'403':
description: The provided credentials were correct but the API is not yet fully configured.
x-example-object:
code: 403
description: The API is not yet fully configured.
message: Forbidden
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-403
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'404':
description: Requested item does not exist.
x-example-object:
code: 404
description: The requested item was not found on the server.
message: Not Found
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-404
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'405':
description: The used HTTP method is not allowed for this URL.
x-example-object:
code: 405
description: The method is not allowed for the requested URL.
message: Method Not Allowed
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-405
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'422':
description: A required parameter is missing or has a wrong structure.
x-example-object:
code: 422
description: The request was well-formed but was unable to be followed due to semantic errors.
message: Unprocessable Entity
status: error
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/error-message-response'
- title: response-status-422
xml:
name: response
namespace: https://apiv2.fleetmon.com
x-extra-attributes:
timestamp:
type: date-time
'429':
description: The client requested the resource too many times. (rate limit)
x-example-object:
code: 429
description: Only 200 requests per 30 days are allowed for this endpoint.
message: Too Many Requests
status: error
content:
application/json:
schema:
allOf:
- $ref
# --- truncated at 32 KB (79 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/fleetmon/refs/heads/main/openapi/fleetmon-fleet-tracker-api-openapi.yml