canonical: https://jentic.com/apis/cruise-itinerary.com/cruise-itinerary # Cruise Itinerary Data API The Cruise Itinerary Data API serves reference data and weekly fare snapshots for cruise lines, ships, ports, and sailings, refreshed every Monday. It searches sailings, returns a sailing's fare history, lists lines, ships, ports, destinations, and regions, and resolves a name to its canonical record in bulk. A price index, a change feed, and weekly bulk exports keep downstream data current, and fares are inventory snapshots rather than live bookable prices. ## For AI agents Query cruise lines, ships, ports, and sailings with weekly fare snapshots, a price index, and a name resolver. Serves reference data and fare history, not live bookings. ## Scope Does not handle cruise booking, cabin availability, or live bookable prices. Use for cruise reference data and weekly fare snapshots only. ## Capabilities - Search sailings by cruise line, ship, port, and date - Retrieve a sailing's fare history from weekly price snapshots - List cruise lines, ships, ports, destinations, and regions - Resolve a cruise line, ship, or port name to its canonical record - Read the latest price index and its historical series - Follow a change feed and download weekly bulk exports ## Use cases ### Agent-Assisted Cruise Search An AI agent connected through Jentic searches sailings for a traveller's dates and destination, then reads each candidate sailing's fare history to show how its weekly snapshot has moved. Because fares are inventory snapshots rather than live bookable prices, the agent presents them as reference pricing and points the traveller to the line to book. Example prompt: Search sailings for a destination and date range, then read the fare history for the top sailing and report its latest snapshot ### Fare Trend Tracking A pricing workflow pulls the price index and a sailing's weekly fare snapshots to track how cruise fares move over time. The index and per-sailing history come from the same source refreshed every Monday, so trend charts stay consistent across lines and ships. Example prompt: Read the latest price index and a specific sailing's fare history to chart how its fare changed week over week ### Cruise Reference Data Sync A data pipeline mirrors cruise lines, ships, ports, destinations, and regions into its own store and keeps them current by following the change feed and downloading the weekly bulk exports. The name resolver maps free-text line and ship names from other systems to canonical records so the data joins cleanly. Example prompt: Download the latest weekly export, then resolve a free-text ship name to its canonical record and reconcile the two ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v1/sailings` | Search sailings | | GET | `/v1/sailings/{id}` | Get a sailing | | GET | `/v1/sailings/{id}/prices` | Fare history of a sailing | | GET | `/v1/lines` | List cruise lines | | GET | `/v1/ships` | List ships | | GET | `/v1/ports` | List ports | | GET | `/v1/price-index/latest` | Latest price index | | GET | `/v1/resolve` | Resolve a name | ## Key resources - **Reference data** — List cruise lines, ships, ports, destinations, and regions - **Sailings** — Search sailings and read a sailing's detail and fare history - **Price index** — Read the latest price index and its historical series - **Exports** — List and download weekly bulk export files and follow the change feed ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 65 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 71 / 100 - AI-Readiness & Agent Experience: 48 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 73 / 100 - **View full report:** https://jentic.com/apis/cruise-itinerary.com/cruise-itinerary/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Cruise Itinerary Data API by hand means choosing between its bearer token and X-API-Key header, remembering that fares are weekly snapshots rather than live prices, and following its change feed to stay current. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The Cruise Itinerary Data API puts the sailing, ship, and port id in the URL path (`/v1/sailings/{id}`), so a rule can pin your agent to the lookups you pick, such as searching sailings and reading fare history. You choose the operations it may call, so bulk export downloads are not included unless you add them. - **Credential handling:** Your Cruise Itinerary Data API credential, whether a bearer token or an X-API-Key, is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search cruise sailings' or 'cruise fare history', and Jentic returns the matching Cruise Itinerary Data operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Amadeus for Developers API** — Covers broad travel inventory including flights and hotels, where Cruise Itinerary focuses on cruise reference data and fare snapshots. - **SeatGeek API** — Supplies events and ticketing for travellers planning around a cruise's ports of call. - **Viator API** — Offers tours and shore excursions at the ports a cruise sailing visits. ## FAQ ### What authentication does the Cruise Itinerary Data API use? The Cruise Itinerary Data API accepts either a bearer token in the Authorization header or an API key in the X-API-Key header per its OpenAPI spec, and every endpoint needs one; a request without a key returns a 401. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context. ### Can I get a sailing's fare history with the Cruise Itinerary Data API? Yes. Each sailing exposes its fare history drawn from weekly snapshots refreshed every Monday. These are inventory snapshots rather than live bookable prices, and a null fare means the cabin is not offered or is sold out, which the feed does not distinguish. ### Can I limit what my agent is allowed to do with the Cruise Itinerary Data API? Yes. Write a rule that allows only the search and lookup operations, such as searching sailings, reading a sailing's fare history, and listing lines and ports, so your agent can query cruise data but cannot download the bulk exports, and every call it makes is logged. ### What are the rate limits for the Cruise Itinerary Data API? The OpenAPI spec does not state numeric rate limits for the Cruise Itinerary Data API; instead each endpoint lists the lowest plan that can call it. Check your plan in the Cruise Itinerary documentation for the request ceilings that apply to your key. ### How do I search cruise sailings with the Cruise Itinerary Data API through Jentic? Search Jentic for 'search cruise sailings' and it returns the sailings-search operation with its input schema; your agent supplies the destination and dates and then reads each sailing's fare history. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a Cruise Itinerary Data MCP server? You don't need an MCP server to give your agent the Cruise Itinerary Data API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the search, lookup, and export operations with scoping and credential isolation applied.