Cruisen Production Web App Cruisen Public API

Name: Cruisen Public API
Brand: Cruisen Public API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey7 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Cruisen Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cruisen Public 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Public API.

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

GET STARTED

Start building with Cruisen Public API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Cruisen Public API for, with concrete tasks.

★ 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.

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.

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.

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 the Jentic vault rather than the agent's 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

7 endpoints — jentic publishes the only available openapi specification for cruisen public api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Cruisen X-API-Key values are stored encrypted in the Jentic vault. Agents receive scoped execution rights and the raw key never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'get my upcoming trips') and Jentic returns the matching get-trips or get-bookings operation along with its parameter schema.

Time to first call

Direct integration: a few hours to wire the X-API-Key header and pagination handling. Through Jentic: minutes — search, load, execute.

FAQs

Specific to using Cruisen Public API through Jentic.

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 at https://app.jentic.com/sign-up.

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.