---
title: "All vessels currently within an area"
method: GET
path: "/api/v0/vessel_inradius"
tags: ["Location Traffic"]
---

# All vessels currently within an area

`GET /api/v0/vessel_inradius`

## Request

- Base URL: `https://api.datalastic.com`
- URL: `https://api.datalastic.com/api/v0/vessel_inradius`
- Auth: one of:
  - API key in header `x-api-key`
  - API key in query parameter `api-key`
- TypeScript: <https://skmtc.dev/datalastic/apis/datalastic-maritime-api/docs/api/v0/vessel_inradius/get.ts> (a function with typed inputs; its response is checked against the schema)

Scan a circular area for all vessels currently inside the radius.

The centre can be static (`lat` + `lon`, or a port by `port_uuid` /
`port_unlocode`) or dynamic, following a vessel by `uuid`, `mmsi`, or
`imo`. Pass exactly one centre. The full result set is returned in a
single response and `data.total` gives the record count.

**Credit cost:** 1 per vessel found, capped at 500 credits per request.

## Query parameters

- `lat` number, float
- `lon` number, float
- `port_uuid` string, uuid
- `port_unlocode` string
- `uuid` string, uuid
- `mmsi` string
- `imo` string
- `radius` number, float, required
- `type` string
- `type_specific` string
- `exclude` string
- `_empty_` boolean
- `nav_status` integer

## Response `200`

Vessels found within the area.

- object
  - `data` VesselLive[]
    - `uuid` string, uuid
    - `name` string
    - `mmsi` string
    - `imo` string
    - `eni` string, nullable: European Number of Identification (inland waterways).
    - `country_iso` string
    - `country_name` string
    - `type` string
    - `type_specific` string
    - `lat` number, float
    - `lon` number, float
    - `speed` number, float: Speed over ground in knots.
    - `course` number, float: Course over ground in degrees (0-360).
    - `heading` number, float: True heading in degrees (0-360).
    - `navigational_status` string
    - `destination` string, nullable
    - `last_position_epoch` integer
    - `last_position_UTC` string, date-time
    - `area` string, nullable
  - `meta` Meta
    - `duration` number, float: Server-side query time in seconds.
    - `endpoint` string
    - `success` boolean
    - `next` string: Pagination token. Present on paginated endpoints (`/vessel_find`) only when more results exist. Pass it back as the `next` query parameter to fetch the following page.

## Other responses

- `400`: Missing required parameter or invalid parameter value.
- `401`: Invalid or expired API key.
- `402`: API key is valid but the credit balance is exhausted or the subscription has expired. Purchase more credits to continue.
- `404`: Requested vessel, port, or resource was not found. No credits deducted.
- `429`: More than 600 API calls in a single minute. The response carries a `Retry-After` header with the wait in seconds. Use it for backoff.
- `500`: Server-side error. Retry the request.

## Changes

- **2026-09-08** `a29cf323d1c3`: 1 breaking, 2 warning, 15 info
  - the `query` request parameter `radius` became required
  - for the `query` request parameter `radius`, the max was set to `50.00`
  - deleted the `query` request parameter `api-key`
  - added the new optional `query` request parameter `_empty_`
  - …14 more

[Operation history](https://skmtc.dev/datalastic/apis/datalastic-maritime-api/changes/api/v0/vessel_inradius/get.md)

---

[API](https://skmtc.dev/datalastic/apis/datalastic-maritime-api.md) - [All operations](https://skmtc.dev/datalastic/apis/datalastic-maritime-api/llms.txt) - [OpenAPI document](https://skmtc.dev/datalastic/apis/datalastic-maritime-api/revisions/2097cdbffcb4?raw)