Cruise Price API

API ID 14256

Search sailings and read the current fare, cabin prices and itinerary, plus recent fare drops across 10 cruise lines.

API Documentation

Endpoints

Request
Returns sailings that match the filters. Each row includes cruise_id, the id used by Cruise Detail, plus the ship, dates, fare and cabin prices. Every filter is optional.
Endpoint ID: 35385
GET https://zylalabs.com/api/14256/cruise+price+api/35385/search+cruises
INPUT PARAMETERS

Search Cruises — Endpoint Features

Object Description
min_duration Optional Minimum cruise length in nights.
max_duration Optional Maximum cruise length in nights.
min_price_eur Optional Minimum per-person fare in euros. Rows without a fare are left out.
max_price_eur Optional Maximum per-person fare in euros.
ship Optional Ship name. Exact match. Separate several names with a comma.
port Optional Port name exactly as the line publishes it, such as Rome (Civitavecchia), Italy.
destination Optional Destination label, such as Mediterranean. Repeat the filter for more than one.
sort Optional Sort field and direction. Default is departure_date:asc. Also price_euro, duration, price_per_night_eur and updated_at.
starting_after Optional Cursor from the previous response next_cursor. Keep the other filters unchanged.
company Optional Cruise line slug, such as princess. Omit it to search every line.
locale Optional Market code such as en_US. It picks the currency and the fare for that market.
limit Optional How many sailings to return. The default is 20. A higher value is capped by the plan.
departure_after Optional Earliest departure date to include, yyyy-mm-dd, inclusive.
departure_before Optional Latest departure date to include, yyyy-mm-dd, inclusive.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

min_duration
max_duration
min_price_eur
max_price_eur
ship
port
destination
sort
starting_after
company
locale
limit
departure_after
departure_before
API EXAMPLE RESPONSE
JSON
{
    "data": [
        {
            "cabin_prices_per_person": {
                "BALCONY": 2319,
                "INTERIOR": 1453
            },
            "company": "princess",
            "cruise_id": "N634",
            "currency": "USD",
            "departure_date": "2026-10-06",
            "destinations": [
                "Mediterranean"
            ],
            "duration": 7,
            "locale": "en_US",
            "ports_list": [
                {
                    "arrival": null,
                    "day": 1,
                    "departure": null,
                    "port": "Rome (Civitavecchia), Italy"
                }
            ],
            "price": 1453,
            "price_euro": 1296.24,
            "price_per_night_eur": 185.18,
            "ship_name": "Enchanted Princess",
            "updated_at": "2026-10-06T06:24:17Z"
        }
    ],
    "has_more": true,
    "next_cursor": null,
    "request_id": "01JSAXEXAMPLE"
}
Search Cruises — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14256/cruise+price+api/35385/search+cruises?company=princess&locale=en_US&limit=5' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Returns one sailing: ship, itinerary, current per-person fare and cabin prices. The id is cruise_id from Search Cruises. Use the same company and locale as that search. Example: N634 for princess and en_US.
Endpoint ID: 35382
GET https://zylalabs.com/api/14256/cruise+price+api/35382/cruise+detail
INPUT PARAMETERS

Cruise Detail — Endpoint Features

Object Description
company Required Cruise line slug. Required, and it must match the company from the Search Cruises row.
locale Required Market code such as en_US. Required. Use the same locale as the search that returned cruise_id.
id Required

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

company
locale
API EXAMPLE RESPONSE
JSON
{
    "data": {
        "cabin_fare_details": null,
        "cabin_prices_per_person": {
            "BALCONY": 2319,
            "INTERIOR": 1453
        },
        "company": "princess",
        "cruise_id": "N634",
        "currency": "USD",
        "departure_date": "2026-10-06",
        "destinations": [
            "Mediterranean"
        ],
        "duration": 7,
        "locale": "en_US",
        "ports_list": [
            {
                "arrival": null,
                "day": 1,
                "departure": null,
                "port": "Rome (Civitavecchia), Italy"
            }
        ],
        "price": 1453,
        "price_euro": 1296.24,
        "price_per_night_eur": 185.18,
        "ship_name": "Enchanted Princess",
        "updated_at": "2026-10-06T06:24:17Z"
    },
    "request_id": "01JSAXEXAMPLE"
}
Cruise Detail — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14256/cruise+price+api/35382/cruise+detail?company=princess&locale=en_US&id=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Returns sailings whose fare fell, with the previous price, the current price and the drop percentage. Every row includes cruise_id, which is the id for Cruise Detail. Every filter is optional.
Endpoint ID: 35384
GET https://zylalabs.com/api/14256/cruise+price+api/35384/recent+price+drops
INPUT PARAMETERS

Recent Price Drops — Endpoint Features

Object Description
company Optional Cruise line slug. Limits the drops to one line. Omit it to include every line.
locale Optional Market code such as en_US. Drops are measured per market. Omit it to include every market.
min_drop_pct Optional Only include drops of at least this percentage. For example, 10 means 10 percent.
since Optional Only drops detected on or after this date, in yyyy-mm-dd, UTC.
limit Optional How many drops to return. The default is 20. A higher value is capped by the plan.
sort Optional Sort field and direction: drop_pct, detected_at or current_price_euro, with :asc or :desc. Default is drop_pct:desc.
starting_after Optional Cursor from the previous response next_cursor. Keep the other filters unchanged.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

company
locale
min_drop_pct
since
limit
sort
starting_after
API EXAMPLE RESPONSE
JSON
{
    "data": [
        {
            "cabin_type": "INTERIOR",
            "company": "princess",
            "cruise_id": "N634",
            "currency": "USD",
            "current_price": 1453,
            "current_price_euro": 1296.24,
            "departure_date": "2026-10-06T00:00:00Z",
            "destinations": [
                "Mediterranean"
            ],
            "detected_at": "2026-10-06T06:24:17Z",
            "drop_amount_euro": 201.76,
            "drop_pct": 13.5,
            "duration": 7,
            "itinerary_url": null,
            "locale": "en_US",
            "previous_price": 1680,
            "previous_price_euro": 1498,
            "ship_name": "Enchanted Princess",
            "title": "Enchanted Princess Mediterranean"
        }
    ],
    "has_more": false,
    "next_cursor": null,
    "request_id": "01JSAXEXAMPLE"
}
Recent Price Drops — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14256/cruise+price+api/35384/recent+price+drops?company=princess&locale=en_US&min_drop_pct=10&since=2026-09-01&limit=5&sort=drop_pct:desc' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Cruise Price API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime.

(Save 2 months with annual billing 🎉)

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Search Cruises returns sailings for a cruise line and a market. Each row includes cruise_id. Copy that value into Cruise Detail and send the same company and locale, because the id is unique only within one line. The example id is N634 for Princess in en_US. A row from Recent Price Drops also includes cruise_id. Cruise Detail returns that sailing: title, ship, departure date, nights, the per-person fare in the market currency and in euros, the nightly euro fare, cabin prices, promotions where the line publishes them, destinations, and the port-by-port itinerary. Recent Price Drops returns sailings whose fare fell, with the previous price, the current price, the drop in euros and the drop percentage. Every filter on Search Cruises and Recent Price Drops is optional.

Cruise Price API FAQs

The Cruise Price API allows you to search for sailings and retrieve current fare information, cabin prices, and detailed itineraries. It also provides access to recent fare drops across 10 different cruise lines.

The `cruise_id` is unique within a specific cruise line and market. When using the `cruise_id` obtained from `Search Cruises` or `Recent Price Drops` to query `Cruise Detail`, you must also provide the same company (cruise line) and locale (market) to ensure accurate retrieval of the sailing's details.

The `Cruise Detail` endpoint provides comprehensive information including the sailing title, ship name, departure date, number of nights, per-person fare in both market currency and euros, the nightly euro fare, detailed cabin prices, available promotions (if published by the cruise line), destinations, and a port-by-port itinerary.

The `Recent Price Drops` endpoint is designed for this purpose. It returns sailings where the fare has recently decreased, providing the previous price, the current price, the amount of the drop in euros, and the percentage of the fare reduction.

Developers can leverage this API to build applications that display real-time cruise pricing, compare fares across different sailings and cruise lines, alert users to price drops, and provide detailed itinerary information. This enables the creation of dynamic travel booking platforms and price tracking tools.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs