CruiseMapper cruise itinerary API
Use the CruiseMapper cruise itinerary API to retrieve quoted price, journey options, journey segments and endpoints, record identities and titles and geographic references as structured JSON from CruiseMapper. Choose record identifier and ship identifier as optional query conditions to select the source records or view required for your request. Use these results to compare cruise itineraries and connect departure dates, ships and ports when researching a sailing. The documented source-page link form identifies the requested entry directly and lets you reuse an existing source-page reference. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
- Selected price
- $0.002 / billing creditPublished pricing
- Sellers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
apishCurrent CruiseMapper cruise itinerary API · GET · View API reference | $0.002 / billing credit | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
arrival_portstringcachedbooleancountintegercredits_usedintegercruise_idintegercurrencystringdatestringdeparture_portstringfetched_atstringitineraryobject[]arrivalnull | stringcountrystringcountry_codestringdate_textstringdayintegerdeparturestring | nullmonthintegerportstringport_idintegerport_urlstringtypestring
ports_of_callintegerprice_fromintegershipobjectidintegernamestringurlstring
titlestring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
arrival_port?: string;
cached?: boolean;
count?: number;
credits_used?: number;
cruise_id?: number;
currency?: string;
date?: string;
departure_port?: string;
fetched_at?: string;
itinerary?: Array<{
arrival?: null | string;
country?: string;
country_code?: string;
date_text?: string;
day?: number;
departure?: string | null;
month?: number;
port?: string;
port_id?: number;
port_url?: string;
type?: string;
}>;
ports_of_call?: number;
price_from?: number;
ship?: {
id?: number;
name?: string;
url?: string;
};
title?: string;
};- Method
- GET
- Endpoint
https://api.openany.si/v1/agent-apis/apish/cruisemapper/v1/cruise- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/apish/cruisemapper/v1/cruise?output=json&raw=0&ship=Wonder+Of+The+Seas' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
id | URL query parametersquery | string | No | The cruise id (`cruise_id` from /cruisemapper/v1/ship/itineraries or /cruisemapper/v1/search). |
ship | URL query parametersquery | string | No | Instead of id: a ship (name, id or link); the route then answers that ship's next cruise. |
raw | URL query parametersquery | string | No | 0 leaves out the bulky `raw` source blocks (often 10-30x smaller). enum: "0", "1" |
fields | URL query parametersquery | string | No | Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included. |
fresh | URL query parametersquery | string | No | 1 skips the 24-hour cache and fetches live. enum: "1" |
output | URL query parametersquery | string | No | JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON are not supported. enum: "json" |
records | URL query parametersquery | string | No | With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row. |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Example from the provider's documentation. Field values in your results will differ.
{
"arrival_port": "Miami, Florida",
"cached": false,
"count": 3,
"credits_used": 1,
"cruise_id": 5328756,
"currency": "USD",
"date": "2026-11-20",
"departure_port": "Miami, Florida",
"fetched_at": "2026-11-19T12:25:44.262Z",
"itinerary": [
{
"arrival": null,
"country": "USA",
"country_code": "US",
"date_text": "20 Nov 16:30",
"day": 20,
"departure": "16:30",
"month": 11,
"port": "Miami, Florida",
"port_id": 40,
"port_url": "https://www.cruisemapper.com/ports/miami-port-40",
"type": "departure"
},
{
"arrival": "07:00",
"country": "Bahamas",
"country_code": "BS",
"date_text": "21 Nov 07:00 - 17:00",
"day": 21,
"departure": "17:00",
"month": 11,
"port": "Coco Cay, Bahamas, Royal Caribbean",
"port_id": 392,
"port_url": "https://www.cruisemapper.com/ports/coco-cay-port-392",
"type": "port_of_call"
},
{
"arrival": "06:30",
"country": "USA",
"country_code": "US",
"date_text": "23 Nov 06:30",
"day": 23,
"departure": null,
"month": 11,
"port": "Miami, Florida",
"port_id": 40,
"port_url": "https://www.cruisemapper.com/ports/miami-port-40",
"type": "arrival"
}
],
"ports_of_call": 1,
"price_from": 347,
"ship": {
"id": 2165,
"name": "Wonder Of The Seas",
"url": "https://www.cruisemapper.com/ships/Wonder-Of-The-Seas-2165"
},
"title": "3 nights, round-trip from Miami, USA"
}Composite rule pricing
Calculated from input parameters and actual returned quantities. Estimate the maximum cost before calling.
Base fee: $0.000000. One matching variant replaces the base fee. Matching add-ons and quantity charges are added.
| Fee item | Price | Metering source | When | Quantity limit |
|---|---|---|---|---|
| Actual API.SH credits consumed | $0.002000 / billing credit | Response · /credits_used · Numeric value | Always | 1 billing credit · Decimal places: 0 |
Each quantity charge is rounded before summing: ceil. Requests exceeding this cost limit are rejected; it is not a price cap: $0.002000.
Response quantities settle after the response. Before execution, the maximum quantity determines the reservation; unused reservation is released. Missing or invalid quantities are not treated as zero.
Pricing parameters and defaults
[]
Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# CruiseMapper cruise itinerary API
Use the CruiseMapper cruise itinerary API to retrieve quoted price, journey options, journey segments and endpoints, record identities and titles and geographic references as structured JSON from CruiseMapper. Choose record identifier and ship identifier as optional query conditions to select the source records or view required for your request. Use these results to compare cruise itineraries and connect departure dates, ships and ports when researching a sailing. The documented source-page link form identifies the requested entry directly and lets you reuse an existing source-page reference. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
## Available implementations
apish · CruiseMapper cruise itinerary API: https://openany.si/markets/apis/capabilities/cruisemapper-cruise-itinerary-api?offering=944e652e-2d63-4862-bdff-9610caa229bf · $0.002 / billing credit
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/cruisemapper-cruise-itinerary-api
Method: GET
Endpoint: https://api.openany.si/v1/agent-apis/apish/cruisemapper/v1/cruise
Price: $0.002 / billing credit
Provider: apish
Contract revision: 2
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/apish/cruisemapper/v1/cruise?output=json&raw=0&ship=Wonder+Of+The+Seas' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'
```
## API contract
```json
{
"resource_type": "api",
"name": "CruiseMapper cruise itinerary API",
"endpoint": "https://api.openany.si/v1/agent-apis/apish/cruisemapper/v1/cruise",
"method": "GET",
"content_type": "none",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "The cruise id (`cruise_id` from /cruisemapper/v1/ship/itineraries or /cruisemapper/v1/search).",
"location": "query",
"name": "id",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Instead of id: a ship (name, id or link); the route then answers that ship's next cruise.",
"location": "query",
"name": "ship",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "0 leaves out the bulky `raw` source blocks (often 10-30x smaller).",
"enum_values": [
"0",
"1"
],
"location": "query",
"name": "raw",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.",
"location": "query",
"name": "fields",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "1 skips the 24-hour cache and fetches live.",
"enum_values": [
"1"
],
"location": "query",
"name": "fresh",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON are not supported.",
"enum_values": [
"json"
],
"location": "query",
"name": "output",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row.",
"location": "query",
"name": "records",
"nullable": false,
"required": false,
"type": "string"
}
],
"billing": {
"currency": "USD",
"mode": "rules",
"parameters": [],
"policy_version": 2,
"sale": {
"addons": [],
"base_price_micro_usd": "0",
"max_cost_micro_usd": "2000",
"quantities": [
{
"id": "upstream_credits",
"label": "Actual API.SH credits consumed",
"max_quantity": "1",
"measure": "value",
"pointer": "/credits_used",
"price_micro_usd": "2000",
"quantity_scale": 0,
"source": "response",
"unit": "credit",
"unit_quantity": "1"
}
],
"rounding": "ceil",
"variants": []
}
},
"examples": [
{
"http_status": 200,
"name": "Official example · Live API.SH response · Minimal request",
"request": {
"body": null,
"headers": {},
"path": {},
"query": {
"output": "json",
"raw": "0",
"ship": "Wonder Of The Seas"
}
},
"response_body": {
"arrival_port": "Miami, Florida",
"cached": false,
"count": 3,
"credits_used": 1,
"cruise_id": 5328756,
"currency": "USD",
"date": "2026-11-20",
"departure_port": "Miami, Florida",
"fetched_at": "2026-11-19T12:25:44.262Z",
"itinerary": [
{
"arrival": null,
"country": "USA",
"country_code": "US",
"date_text": "20 Nov 16:30",
"day": 20,
"departure": "16:30",
"month": 11,
"port": "Miami, Florida",
"port_id": 40,
"port_url": "https://www.cruisemapper.com/ports/miami-port-40",
"type": "departure"
},
{
"arrival": "07:00",
"country": "Bahamas",
"country_code": "BS",
"date_text": "21 Nov 07:00 - 17:00",
"day": 21,
"departure": "17:00",
"month": 11,
"port": "Coco Cay, Bahamas, Royal Caribbean",
"port_id": 392,
"port_url": "https://www.cruisemapper.com/ports/coco-cay-port-392",
"type": "port_of_call"
},
{
"arrival": "06:30",
"country": "USA",
"country_code": "US",
"date_text": "23 Nov 06:30",
"day": 23,
"departure": null,
"month": 11,
"port": "Miami, Florida",
"port_id": 40,
"port_url": "https://www.cruisemapper.com/ports/miami-port-40",
"type": "arrival"
}
],
"ports_of_call": 1,
"price_from": 347,
"ship": {
"id": 2165,
"name": "Wonder Of The Seas",
"url": "https://www.cruisemapper.com/ships/Wonder-Of-The-Seas-2165"
},
"title": "3 nights, round-trip from Miami, USA"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Official example · Live API.SH response · Minimal request
Example from the provider's documentation. Field values in your results will differ.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 7
Review these request fields before running. Keep the published provider and request method unchanged.
id- The cruise id (`cruise_id` from /cruisemapper/v1/ship/itineraries or /cruisemapper/v1/search).
ship- Instead of id: a ship (name, id or link); the route then answers that ship's next cruise.
raw- 0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
fields- Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
fresh- 1 skips the 24-hour cache and fetches live.
output- JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON are not supported.
records- With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/apish/cruisemapper/v1/cruise?output=json&raw=0&ship=Wonder+Of+The+Seas' \ -X GET \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json'Check the response
Sample response · Documented HTTP 200
Sample response{ "arrival_port": "Miami, Florida", "cached": false, "count": 3, "credits_used": 1, "cruise_id": 5328756, "currency": "USD", "date": "2026-11-20", "departure_port": "Miami, Florida", "fetched_at": "2026-11-19T12:25:44.262Z", "itinerary": [ { "arrival": null, "country": "USA", "country_code": "US", "date_text": "20 Nov 16:30", "day": 20, "departure": "16:30", "month": 11, "port": "Miami, Florida", "port_id": 40, "port_url": "https://www.cruisemapper.com/ports/miami-port-40", "type": "departure" }, { "arrival": "07:00", "country": "Bahamas", "country_code": "BS", "date_text": "21 Nov 07:00 - 17:00", "day": 21, "departure": "17:00", "month": 11, "port": "Coco Cay, Bahamas, Royal Caribbean", "port_id": 392, "port_url": "https://www.cruisemapper.com/ports/coco-cay-port-392", "type": "port_of_call" }, { "arrival": "06:30", "country": "USA", "country_code": "US", "date_text": "23 Nov 06:30", "day": 23, "departure": null, "month": 11, "port": "Miami, Florida", "port_id": 40, "port_url": "https://www.cruisemapper.com/ports/miami-port-40", "type": "arrival" } ], "ports_of_call": 1, "price_from": 347, "ship": { "id": 2165, "name": "Wonder Of The Seas", "url": "https://www.cruisemapper.com/ships/Wonder-Of-The-Seas-2165" }, "title": "3 nights, round-trip from Miami, USA" }
Common questions
Do I need a separate key for every provider?
Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.
Are these providers interchangeable?
No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.
How is this API billed?
API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.
Where do the price and contract come from?
The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.
How do OpenAny Balance and x402 differ?
OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.
Does Playground send a paid request?
Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.
Use CruiseMapper cruise itinerary API with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.