> ## Documentation Index > Fetch the complete documentation index at: https://docs.gdeltcloud.com/llms.txt > Use this file to discover all available pages before exploring further. # One vessel's track over time > ⚠️ RAW position track for a single vessel by IMO — the literal 'this ship over time': every AIS fix (time, position, speed, course, heading, nav status) across the window, time-ordered. Keyset-paginated: follow the opaque next_cursor to stitch a long window into pages rather than one giant response. Requires a plan with Maritime intelligence access (`can_use_maritime`) — the Corporate & Supply Chain plan and above. Historical / baseline surface: reads raw AIS positions directly. Forward-accruing: positions begin at launch (June 2026) — no historical backfill. Terrestrial AIS only (no satellite). Date windows are capped at 30 days; defaults to the trailing 7 days. ## OpenAPI ````yaml /api-reference/openapi-v2.json get /api/v2/maritime/vessels/{imo}/track openapi: 3.0.3 info: title: GDELT Cloud API v2 version: 2.0.0 description: >- Clean v2 REST API for generated GDELT Cloud structured Events, clustered Stories, linked Entities, summaries, admin1 discovery, significance ranking, and paginated article evidence. Event significance is a family-scoped weighted blend, renormalized so every event family spans a true 0-1: each event's raw total is divided by the maximum its own family can reach (Conflict 1.00, CAMEO+ POLITICAL 0.90, other CAMEO+ domains 0.65). All events: Goldstein severity 0.25, article evidence 0.05, confidence 0.05. Conflict only: fatalities 0.55 (log-scaled by body count) and civilian targeting 0.10. CAMEO+ only: magnitude 0.20, systemic importance 0.15, propagation potential 0.10, market sensitivity 0.10. When magnitude is unmeasured its term AND its 0.20 weight are both dropped. The four CAMEO+ metrics are rubric scores produced by published formulas - ordinal ranking signals, not measurements, probabilities, or predicted price moves. goldstein_scale is one canonical public metric, populated for Conflict Events and CAMEO+ POLITICAL Events where meaningful. Story linked_event_count is a Story-to-Event link aggregate, not a distinct Event total. servers: - url: https://gdeltcloud.com description: Production - url: http://localhost:3000 description: Local development security: - ApiKeyAuth: [] tags: - name: Events description: Coded CAMEO+ / conflict events — search, fetch, and summarize. - name: Stories description: Clustered narratives (stories) and their articles. - name: Entities description: >- People & organizations — resolve a name to an entity, then fetch its profile and tone. - name: Geography description: Admin-1 geography lookups. - name: Energy description: Global Energy Monitor assets + ownership registry. - name: Facilities description: >- Unified physical-asset directory — GEM energy assets + World Port Index ports + Epoch AI data centers on one keyed surface, resolved to spine owners. Plan-gated (Analyst plan and up). - name: Screening and Reference description: >- Restricted-party lists, screening, and ownership-chain exposure. Plan-gated (`can_use_screening` / `can_use_exposure`). - name: China description: >- China overseas development finance (AidData GCDF). Plan-gated (`can_use_china`). - name: Media Intelligence description: >- Entity tone (`can_use_tone`) and Share of Voice (`can_use_share_of_voice`) are plan-gated. Social signal remains an admin-only preview. - name: Filings description: >- SEC EDGAR filings, XBRL financials, and AI-extracted relations. Requires a plan with SEC filings access (`can_use_filings`) — the Corporate & Supply Chain plan and above. - name: Macro Finance description: >- FRED economic time series (catalog, point-in-time observations, releases). Plan-gated (`can_use_macro`). - name: Maritime description: >- AIS-derived vessel-flow signals across maritime chokepoints — chokepoint transits, last-known vessel positions, carriers, dwell, and AIS-dark gaps. Plan-gated (`can_use_maritime`). - name: Briefs description: Source-backed monitoring briefs. paths: /api/v2/maritime/vessels/{imo}/track: get: tags: - Maritime summary: One vessel's track over time description: >- ⚠️ RAW position track for a single vessel by IMO — the literal 'this ship over time': every AIS fix (time, position, speed, course, heading, nav status) across the window, time-ordered. Keyset-paginated: follow the opaque next_cursor to stitch a long window into pages rather than one giant response. Requires a plan with Maritime intelligence access (`can_use_maritime`) — the Corporate & Supply Chain plan and above. Historical / baseline surface: reads raw AIS positions directly. Forward-accruing: positions begin at launch (June 2026) — no historical backfill. Terrestrial AIS only (no satellite). Date windows are capped at 30 days; defaults to the trailing 7 days. operationId: get-maritime-vessel-track-v2 parameters: - name: imo in: path required: true schema: type: string description: IMO number of the vessel (e.g. 9006681). - name: date_start in: query required: false schema: type: string description: Window start YYYY-MM-DD (≤30-day window). - name: date_end in: query required: false schema: type: string description: Window end YYYY-MM-DD. - name: days in: query required: false schema: type: integer minimum: 1 maximum: 30 description: Trailing N-day window (1–30). Defaults to 7. - name: limit in: query required: false schema: type: integer default: 1000 minimum: 1 maximum: 5000 description: Position points per page (1–5000). - name: cursor in: query required: false schema: type: string description: >- Opaque keyset cursor on (time, mmsi). Pass back a prior response's next_cursor to fetch the next page; do not request one giant response. responses: '200': description: >- A page of the vessel's raw position track, time-ordered ascending. Envelope: { success, imo, data, pagination, applied_filters }. Each data row: time, mmsi, lat, lon, sog, cog, heading, nav_status, chokepoint. pagination.next_cursor is an opaque token — follow it to page through a long window. content: application/json: schema: type: object properties: success: type: boolean imo: type: string data: type: array items: type: object properties: time: type: string mmsi: type: integer lat: type: number lon: type: number sog: type: number cog: type: number heading: type: integer nav_status: type: string chokepoint: type: string pagination: type: object properties: limit: type: integer cursor: {} next_cursor: type: string applied_filters: type: object properties: date_start: type: string date_end: type: string ignored: type: object properties: {} examples: example: summary: GET /api/v2/maritime/vessels/{imo}/track — example response value: success: true imo: '9006681' data: - time: '2026-06-12 03:14:07' mmsi: 636019825 lat: 25.9831 lon: 56.7042 sog: 13.1 cog: 298.4 heading: 301 nav_status: under_way chokepoint: hormuz - time: '2026-06-12 04:46:52' mmsi: 636019825 lat: 26.4127 lon: 56.2188 sog: 12.6 cog: 305.2 heading: 307 nav_status: under_way chokepoint: hormuz pagination: limit: 1000 cursor: null next_cursor: MjAyNi0wNi0xMiAwNDo0Njo1Mnw2MzYwMTk4MjU= applied_filters: date_start: '2026-06-05' date_end: '2026-06-12' ignored: {} '400': description: Missing/invalid IMO (MISSING_PARAM) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Missing/invalid API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: >- Plan required (PLAN_REQUIRED) — the caller's plan does not carry the required source entitlement. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - ApiKeyAuth: [] components: schemas: ErrorResponse: type: object properties: success: type: boolean enum: - false error: type: string code: type: string details: type: object description: >- Recoverable validation context when available, such as param, invalid_value, accepted_values, nearest_values, and a corrected example. additionalProperties: true securitySchemes: ApiKeyAuth: type: http scheme: bearer bearerFormat: gdelt_sk_... description: 'GDELT Cloud API key. Send as `Authorization: Bearer gdelt_sk_...`.' ````