canonical: https://jentic.com/apis/cruisen-production.web.app/cruisen-production

# Cruisen Production Web App Cruisen Public API

Jentic publishes the only available OpenAPI specification for Cruisen Public API, keeping it validated and agent-ready. Cruisen is a travel-advisor platform that exposes seven read-only endpoints for retrieving authenticated user info, traveller profiles, bookings, and trip details. All requests authenticate with an X-API-Key header issued to authorised travel advisors.

## For AI agents

Read travel-advisor bookings, trips, and traveller profiles from the Cruisen platform using a single API key.

## Scope

Does not handle booking creation, payment processing, or itinerary modification - use for read-only travel advisor data lookups only.

## Capabilities

- Retrieve the authenticated travel advisor's user record
- Look up a single traveller profile by ID or list profiles by request type
- Fetch every booking attached to the authenticated advisor
- Pull a specific booking record by booking ID
- List every trip belonging to the authenticated user
- Fetch a single trip's full itinerary by trip ID

## Use cases

### Travel Advisor Booking Dashboard

Pull every booking and trip for an authenticated advisor to populate a daily dashboard showing upcoming departures, traveller contact details, and itinerary status. The seven GET endpoints cover the full read surface needed for advisor-facing tooling.

Example prompt: Call GET /get-bookings to list all advisor bookings, then for each booking call GET /get-trip with the trip ID and assemble a daily departure summary.

### Client Profile Lookup Before a Call

Retrieve a traveller's saved profile (preferences, contact info, history) immediately before an advisor takes a client call so the advisor opens the conversation already aware of the client's context.

Example prompt: Call GET /get-profile with the client's profile ID and surface their stored preferences and contact info to the advisor.

### Trip Itinerary Sync to Internal Tools

Mirror Cruisen trip and booking records into an internal CRM, calendar, or accounting system by polling /get-bookings and /get-trips on a schedule. Because the API is read-only, integrations stay safe - no risk of accidentally mutating live booking state.

Example prompt: Poll GET /get-trips every 15 minutes, diff against last cached state, and upsert any new or changed trip records into the connected CRM.

### Agent-Driven Travel Concierge

Allow an AI concierge agent to answer traveller questions ('When does my next trip depart?', 'What's on my profile?') by calling the Cruisen API on demand through Jentic, with the X-API-Key managed by your Jentic One instance rather than the agent's prompt.

Example prompt: Search Jentic for 'get my upcoming trips', load the get-trips operation, and call it with the advisor's stored API key to answer the traveller's question.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/get-user` | Get authenticated advisor user info |
| GET | `/get-bookings` | List all bookings for the advisor |
| GET | `/get-booking` | Get a single booking by ID |
| GET | `/get-trips` | List all trips for the user |
| GET | `/get-trip` | Get a single trip by ID |
| GET | `/get-profile` | Get a single profile by ID |
| GET | `/get-profiles` | List profiles by request type |

## Key resources

- **User** — Authenticated advisor account information.
- **Profiles** — Traveller profile records - single fetch by ID or list by request type.
- **Bookings** — Booking records belonging to the authenticated advisor.
- **Trips** — Trip itinerary records belonging to the authenticated user.

## Why Jentic

- **Setup:** Wiring the Cruisen Public API by hand means setting its X-API-Key header and threading the read-only user, booking, trip, and profile lookups yourself. Through Jentic you install once, import the Cruisen Public API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Cruisen Public API is read-only, so limit the agent to the operations it needs, such as get-trips or get-bookings. You choose the operations it may call, so profile reads are not included unless you add them.
- **Credential handling:** 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.
- **Discovery method:** Agents search Jentic by intent such as 'get my upcoming trips' or 'list my bookings', 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

- **Cruisen API** — Companion Cruisen surface in the same vendor family.
- **Cruise Control API** — Different cruise-themed product focused on review automation rather than travel bookings.
- **Crustdata API** — Enrich traveller or company records with external data points.

## FAQ

### Why is there no official OpenAPI spec for Cruisen Public API?

Cruisen does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cruisen Public 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 Public API use?

The API uses an API key supplied in the X-API-Key request header. Keys are issued to authorised travel advisors. Through Jentic, the key is held in the encrypted vault and the agent never sees its raw value.

### Can I create or update bookings with the Cruisen Public API?

No. The current spec only exposes GET endpoints for users, profiles, bookings, and trips. The API is read-only - booking creation and mutation must be performed through Cruisen's internal advisor tooling.

### How do I list every trip for an advisor through the Cruisen Public API?

Call GET /get-trips with a valid X-API-Key. The response returns every trip belonging to the authenticated user. Use GET /get-trip with a trip ID for a single record.

### What are the rate limits for the Cruisen Public API?

The OpenAPI specification does not document specific rate limits. Watch for HTTP 429 responses and contact Cruisen support to confirm production quotas before running large-scale syncs.

### How do I fetch a traveller profile through Jentic?

Run pip install jentic, then search 'look up a traveller profile', load the get-profile operation, and execute it with the profile ID. Jentic resolves auth and parameter schema so the agent only supplies the ID.

### Can I limit what my agent is allowed to do with the Cruisen Public API?

Yes. Because you run Jentic One yourself, your own rules decide which of the Cruisen Public API's read-only operations the agent may call, so you can allow only get-trips and get-bookings while excluding profile reads such as get-profile and get-profiles unless you add them. Your Cruisen X-API-Key is stored once by your own instance and injected at execution time, so the agent never sees its raw value. The agent can only reach the endpoints you permit.