Update Boat

Edit the details of a boat your company owns. Send only the fields you want to change; every field left out keeps its value. After every save the boat's completeness is checked again, so an update can publish a boat that became complete — or unpublish one that no longer is.

Authentication

Requires one of:

• API key: X-API-Key header with your API key. This is the way to call it from your own systems.
• Session: a signed-in charter.boats session — what the dashboard uses from the browser. Outside charter.boats a request without a key is stopped by bot protection (HTML 403), so integrations should use the key.

Either way, the account must be a member of the company that owns the boat. Changing pricing_source additionally needs an admin or owner of that company.

Path Parameters

Request Body

Sending "" for a number field clears it (stored as null).

Fields not listed are ignored. So are fields a connected platform owns on a boat it prices — on an MMK-priced boat manufacturer_id, model, location_id, skipper and security_deposit, on a Nausys-priced boat manufacturer_id, model, location_id and skipper — which the platform's sync rewrites; they are skipped silently, not rejected. Switch pricing_source to direct to edit them. The four check-in fields are not among them: on a boat MMK or Nausys prices, a value you set is kept by later syncs.

Request

curl -X PATCH https://charter.boats/api/boats/550e8400-e29b-41d4-a716-446655440000 \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{
    "capacity": 10,
    "location_id": 11336,
    "security_deposit": 2500
  }'

Response

The boat after the update, with the fields your dashboard's boat editor reads, plus:

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "title": "BALI Catspace - Luxury Catamaran",
  "capacity": 10,
  "location_id": 11336,
  "security_deposit": 2500,
  "is_published": false,
  "missing": ["At least one image"],
  "auto_unpublished": false,
  "skipped_fees": []
}

Errors