---
title: "Ship sales, purchase, and demolition records"
method: GET
path: "/api/maritime_reports/spd"
tags: ["Add-ons - Sales & Demolitions"]
---

# Ship sales, purchase, and demolition records

`GET /api/maritime_reports/spd`

## Request

- Base URL: `https://api.datalastic.com`
- URL: `https://api.datalastic.com/api/maritime_reports/spd`
- 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/maritime_reports/spd/get.ts> (a function with typed inputs; its response is checked against the schema)

Returns transaction records: seller, buyer, sale price (total and per
LDT), sales type, and dry dock dates at time of sale.

**Credit cost:** 1 per record returned. Requires an Add-Ons plan tier.

For a **bulk export**, POST to `/api/v0/report` with
`report_type: sales_purchase_demolitions`. Bulk reports cost 2,000 credits each.

## Query parameters

- `imo` string
- `name` string
- `from` string, date
- `to` string, date

## Response `200`

Matching sale/demolition records.

- object
  - `data` ShipSPD[]
    - `id` integer
    - `sales_report_date` string, date
    - `imo` string
    - `vessel_name` string
    - `flag_name` string
    - `vessel_type_code` string
    - `built_year` string
    - `dwt_design` integer: Design deadweight tonnage.
    - `gt` integer: Gross tonnage.
    - `ldt` integer: Lightweight displacement tonnage.
    - `seller` string, nullable
    - `buyer` string, nullable
    - `sales_price_usd_mio` number, nullable: Sale price in millions USD.
    - `sales_price_usd/ldt` number, nullable: Sale price in USD per LDT.
    - `destination` string, nullable
    - `sales_type` string, nullable
    - `dry_dock_date` string, date, nullable
    - `special_survey_date` string, date, nullable
    - `sales_note` string, nullable
    - `previous_sales_record` string, nullable
    - `modified_at` string, date-time
  - `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 warning, 7 info
  - deleted the `query` request parameter `api-key`
  - added the media type `application/json` for the response with the status `401`
  - added the non-success response with the status `400`
  - added the non-success response with the status `402`
  - …4 more

[Operation history](https://skmtc.dev/datalastic/apis/datalastic-maritime-api/changes/api/maritime_reports/spd/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)