## tripadvisor/cruise

`GET /v1/tripadvisor/cruise`

A cruise ship page: name, image, average rating and review count with the rating histogram, passengers, crew, passenger-to-crew and passenger-to-space ratios, launch year, cabin types and sizes, photo categories, whether itineraries are listed, and the newest reviews on the page. Re-wired 6 Sep 2026 on the platform's own reader (migration 191).

*Cruise ship*

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | no | The ship page URL (Cruise_Review-d<id>-Reviews-<name>). Send this, or ship_id with ship_name. — e.g. `https://www.tripadvisor.com/Cruise_Review-d15691709-Reviews-Pearl_Mist` |
| `ship_id` | no | Ship id (the number after d in the page URL, as tripadvisor/cruises gives it) — e.g. `15691709` |
| `ship_name` | no | The ship name as it appears in the page URL — e.g. `Pearl Mist` |
| `dry_run` | no | Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution. — e.g. `1` |

**Cost:** 2 credits at list price per successful uncached response; variable-cost operations may quote or settle a different charge. Confirmed uncharged or refunded failures report zero. Pending reconciliation can report credits_used:null; retain request_id and the original idempotency key.

```bash
curl "https://www.monocrawl.com/v1/tripadvisor/cruise?url=https%3A%2F%2Fwww.tripadvisor.com%2FCruise_Review-d15691709-Reviews-Pearl_Mist" \
  -H "x-api-key: mn_your_key_here"
```

### Response data

Illustrative abbreviated data; documented core fields are optional and may be null. Additional source fields are allowed.

```json
{
  "ship_id": "123",
  "name": "Example ship"
}
```

[Field reference](https://www.monocrawl.com/docs/endpoints/tripadvisor/cruise#response) · [JSON Schema for response.data](https://www.monocrawl.com/schemas/tripadvisor/cruise.json)