Cruisen API
Agent-ready OpenAPI document · curated by JenticProductivityCollaborationapiKey7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read cruise travel advisor users, profiles, bookings, and trips through a small, single-key API surface.
Use for: Get the authenticated cruise advisor's user record, Retrieve all bookings I have access to, Find the trip itinerary for a specific cruise booking, List every traveller profile in my advisor account
Not supported: Does not handle booking creation, payment processing, or cabin assignment - use for read-only cruise advisor data lookups only.
Jentic publishes the only available OpenAPI specification for Cruisen API, keeping it validated and agent-ready. Cruisen is a platform for cruise travel advisors that exposes seven read-only endpoints covering the authenticated user, traveller profiles, bookings, and trip itineraries. Authentication is handled through a single X-API-Key header issued to authorised advisors.
Install Jentic One Beta
Connect the Cruisen API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cruisen API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcruisen.com%2Fcruisen" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcruisen.com%2Fcruisen" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Cruisen API.
Identify the authenticated cruise advisor through GET /get-user
Fetch a single traveller profile or list every profile the advisor can see
Retrieve every booking attached to the advisor's account
Pull a specific booking record by booking ID
List every cruise trip belonging to the advisor
Get full trip itinerary detail by trip ID
Use Cases
Patterns agents use Cruisen API for, with concrete tasks.
★ Cruise Departure Briefings
Generate pre-departure briefings for cruise advisors by reading every upcoming trip and matching booking details, then formatting a per-day summary of who is sailing and on which itinerary.
Call GET /get-trips, filter to trips departing in the next 7 days, fetch each linked booking via GET /get-booking, and assemble a briefing document.
Traveller Profile Sync
Mirror traveller profile data from Cruisen into a CRM or marketing platform by polling /get-profiles and upserting changed records. Because the API is GET-only, the sync direction is always Cruisen-to-CRM and never the reverse.
Call GET /get-profiles with the relevant request type, diff against the CRM cache, and upsert any new or changed profile records.
Booking Verification for Customer Service
Look up a booking by its Cruisen ID when a traveller calls in, returning the linked profile and trip so the advisor can confirm details immediately without leaving the agent interface.
Given a booking ID from the customer, call GET /get-booking, then GET /get-trip and GET /get-profile for the linked records, and present the consolidated detail to the advisor.
Agent-Driven Cruise Concierge
Allow an AI concierge agent to answer cruise questions on behalf of an advisor - 'Which of my clients are sailing next week?', 'What's on John Smith's profile?' - by routing structured calls through Jentic so the advisor's API key stays in the vault.
Search Jentic for 'list my upcoming cruise trips', load the get-trips operation, and execute it with the advisor's stored credential.
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for cruisen api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/get-user
Get the authenticated advisor user
GET
/get-bookings
List all bookings
GET
/get-booking
Get a single booking
GET
/get-trips
List all trips
GET
/get-trip
Get a single trip
GET
/get-profiles
List all profiles
GET
/get-profile
Get a single profile
GET
/get-user
Get the authenticated advisor user
GET
/get-bookings
List all bookings
GET
/get-booking
Get a single booking
GET
/get-trips
List all trips
GET
/get-trip
Get a single trip
GET
/get-profiles
List all profiles
GET
/get-profile
Get a single profile
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Cruisen API by hand means setting its X-API-Key header and threading the read-only user, booking, trip, and profile lookups yourself against the cruisen-production host. Through Jentic you install once, import the Cruisen API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The Cruisen API is read-only, so limit the agent to the operations it needs, such as get-trips or get-booking. You choose the operations it may call, so profile reads are not included unless you add them.
Credential isolation
Your Cruisen 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.
Intent-based discovery
Agents search Jentic by intent such as 'list my upcoming cruise trips' or 'look up a booking', and Jentic returns the matching Cruisen operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cruisen API through Jentic.
Why is there no official OpenAPI spec for Cruisen API?
Cruisen does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cruisen API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Cruisen API use?
Requests authenticate with an X-API-Key header. Keys are issued to authorised cruise advisors. Through Jentic the key is held in the encrypted vault so the agent never receives its raw value.
Can I create new bookings with the Cruisen API?
No. The spec only exposes GET endpoints for users, profiles, bookings, and trips. Booking creation must be handled in Cruisen's own advisor tooling - the API is read-only.
How do I retrieve all my cruise trips through the Cruisen API?
Call GET /get-trips with a valid X-API-Key. The response lists every trip linked to the authenticated advisor. For a single trip, use GET /get-trip with the trip ID.
What are the rate limits for the Cruisen API?
The OpenAPI specification does not document numeric rate limits. Watch for HTTP 429 responses on heavy traffic and contact Cruisen support to confirm production quotas.
How do I look up a traveller profile via Jentic?
Run pip install jentic, search 'look up a cruise traveller profile', load the get-profile operation, and execute it with the profile ID. Jentic injects the X-API-Key automatically.
Can I limit what my agent is allowed to do with the Cruisen API?
Yes. Because you run Jentic One yourself, your own rules decide which of the Cruisen API's read-only operations the agent may call and which credential it uses. The Cruisen API is entirely read-only, so you can restrict the agent to just the operations it needs, such as get-trips or get-booking, and leave profile reads like get-profiles or get-profile out unless you explicitly add them. Nothing beyond the operations you grant is reachable, and booking creation is impossible since the API exposes no write endpoints.
GET STARTED