A. Mylne & Co.

Mylne Archive API

Version 1 provides read-only access to the public Mylne Yacht Register and Design Archive. It is designed for carefully attributed integrations, including Classic Yacht Info.

Yachts

Search the register and retrieve public yacht details, photographs and consent-safe ownership history.

Designs

Retrieve design details, associated yachts and deliberately low-resolution drawing previews.

Privacy-first

Personal contact details, internal notes and full-resolution drawings are never exposed.

Getting started

Create a personal API key after signing in, then send it in the X-API-Key header with every V1 request.

curl "https://api.mylne.com/v1/yachts/the-blue-peter-2011/" \
  -H "X-API-Key: mylne_v1_your_key_here"

What a yacht record contains

A yacht detail request returns the archive record plus the two primary visual fields that are most useful for an integration. This is an excerpt from /v1/yachts/the-blue-peter-2011/; values not shown are omitted for brevity.

{
  "data": {
    "name": "The Blue Peter",
    "year_built": "1930",
    "primary_photo_url": null,
    "linked_design": {
      "design_number": 315,
      "name": "The Blue Peter",
      "designer": "Alfred Mylne",
      "year_of_design": 1928,
      "url": "https://www.mylne.com/design-archive/designs/315-the-blue-peter/"
    },
    "primary_design_image": {
      "scan_number": 10022,
      "thumbnail_url": "https://…",
      "thumbnail_rotation": 0,
      "is_design_cover": true
    }
  }
}

primary_photo_url is the selected public yacht photograph. It is null when no public primary photo is available.

primary_design_image is a low-resolution drawing thumbnail for the linked design. It can be null when there is no published thumbnail.

is_design_cover: true means the archive's designated cover drawing was used. When it is false, the API has selected the first available published thumbnail instead.

linked_design.url is the canonical Mylne Archive page. Use it when linking readers back to the archive.

Version 1 endpoints

GET /v1/yachts
GET /v1/yachts/{slug}
GET /v1/designs/{number}
GET /v1/designs/{number}/drawings
GET /v1/recent-activity

OpenAPI 3.1 specification

Please cache responses. Keys can be revoked at any time from your account.

Search and pagination

Yacht lists accept q, year_built, exists_status, design_id, page and per_page. Results include total, page and per_page; the maximum page size is 100.

GET /v1/yachts/?q=blue%20peter&per_page=10
GET /v1/yachts/?exists_status=Yes&page=2&per_page=30

Use images responsibly

The API provides public photos and deliberately low-resolution drawing previews for display in an attributed integration. When displaying a Mylne image or record, credit A. Mylne & Co., Mylne Archive and link to the supplied canonical Mylne URL where available.

Do not present a thumbnail as a licensed full-resolution drawing, remove its provenance, or use it as your own asset. Full-resolution drawings are not available through V1.

Authentication, browsers and caching

Every /v1/ request requires a personal key in X-API-Key. The API accepts cross-origin requests, but keep keys on your server: a key embedded in browser code can be copied and abused.

Responses send Cache-Control: public, max-age=60, s-maxage=300. Cache at your edge or server for up to five minutes, and treat Mylne as the source of record.

Errors you should handle

401: — missing, invalid or revoked API key.
400: — malformed identifier, such as an invalid yacht slug.
404: — no public record matches the requested yacht, design or route.
5xx: — retry with sensible backoff; please avoid rapid repeated requests.