canonical: https://jentic.com/apis/jurny.com/jurny

# Jurny API

Jentic publishes the only available OpenAPI specification for Jurny API, keeping it validated and agent-ready. Jurny is a vacation rental and short-term rental operations platform. The API exposes endpoints to create and list properties, manage reservations, and look up guest profiles, giving property managers a programmatic surface for the same data the Jurny dashboard surfaces. It is suited for syncing inventory and bookings between Jurny and external channel managers, accounting tools, or guest-facing apps.

## For AI agents

Manage short-term rental properties, reservations, and guest profiles in Jurny from code or an AI agent.

## Scope

Does not handle payment capture, channel-listing distribution, or smart-lock device control - use for property, reservation, and guest data only.

## Capabilities

- Create new short-term rental properties via POST /properties with address and configuration data
- List the property portfolio with GET /properties for syncing inventory to channel managers
- Retrieve a single property's full record using GET `/properties/{property_id}`
- Create reservations against a property through POST /reservations
- List reservations across the portfolio with GET /reservations for revenue and occupancy reporting
- Pull guest profile detail with GET `/guests/{guest_id}` to populate CRM or check-in flows

## Use cases

### Channel-Manager Booking Sync

Property managers using Airbnb or Booking.com alongside Jurny need new reservations to land in Jurny without manual entry. A worker reads bookings from each channel and POSTs them via /reservations on Jurny, then GET /reservations confirms the create. This keeps cleaning and check-in workflows aligned with the actual booking calendar.

Example prompt: For each new Airbnb booking, call POST /reservations with the property_id, guest detail, and check-in/out dates, then GET /reservations to confirm the booking exists.

### Owner Portfolio Onboarding

When a new owner brings a portfolio of homes onto Jurny, the operations team scripts the onboarding by POSTing each property to /properties with address, room counts, and amenities. GET /properties is then used to verify the import matches the source spreadsheet. A 50-property portfolio can be onboarded in minutes rather than a day of dashboard clicking.

Example prompt: For each row in 'new-owner-portfolio.csv', call POST /properties with the address and bedroom count, then GET /properties to verify all rows imported.

### Guest CRM Hydration

Concierge teams want a unified guest profile for every reservation, including past stays. GET `/guests/{guest_id}` returns the guest record, which a CRM hydrator merges with reservation history from /reservations. The result is a single guest view used to personalise check-in, upsell, and follow-up.

Example prompt: For each reservation in the next 7 days, fetch the guest with GET `/guests/{guest_id}` and write a unified record to the CRM with name, email, and prior stay count.

### Agent-Driven Booking Assistant

An AI assistant for a property manager can book a stay on a specific property via Jentic. The agent searches 'create a reservation', loads POST /reservations, and executes with property and guest detail provided in the conversation. This puts a Jurny booking action behind a chat prompt without exposing the manager's API key.

Example prompt: Through Jentic, search 'create a reservation', load POST /reservations, and execute with property_id 'prop-42', guest 'jane@example.com', check-in '2026-07-10', check-out '2026-07-15'.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/properties` | Create a short-term rental property |
| GET | `/properties` | List properties in the portfolio |
| GET | `/properties/{property_id}` | Retrieve a specific property |
| POST | `/reservations` | Create a reservation for a property |
| GET | `/reservations` | List reservations |
| GET | `/guests/{guest_id}` | Retrieve a guest profile |

## Key resources

- **Properties** — Create, list, and retrieve short-term rental property records
- **Reservations** — Create and list bookings against properties
- **Guests** — Retrieve guest profile detail by guest ID

## Why Jentic

- **Setup:** Wiring the Jurny API by hand means learning its API key auth and threading property, reservation, and guest ids through each call yourself. Through Jentic you install once, import the Jurny API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Jurny puts the property id in the URL path (`/properties/{property_id}`), so a rule can pin your agent to one property: it can read that property and nothing else. You choose the operations it may call, so ones like creating reservations are not included unless you add them.
- **Credential handling:** Your Jurny 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 'create a reservation' or 'list my properties', and Jentic returns the matching Jurny operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hostfully API** — Vacation rental property management platform with overlapping property and reservation surfaces.
- **Cloudbeds API** — Hospitality platform covering hotels and vacation rentals with channel management built in.
- **Stripe API** — Pair Jurny reservations with Stripe to capture deposits and final payments.

## FAQ

### Why is there no official OpenAPI spec for Jurny API?

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

The Jurny API uses an API key authentication scheme. The key is sent on every request and identifies the property-management account. Through Jentic the key is held in the encrypted vault and never exposed to the agent runtime.

### Can I create reservations programmatically with the Jurny API?

Yes. POST /reservations creates a booking against a property with guest detail and dates, and GET /reservations lists existing bookings for confirmation or reporting.

### What are the rate limits for the Jurny API?

Jurny applies per-account rate limits that vary with plan tier; the spec does not pin a fixed value. Use exponential backoff on 429 responses and cache property lookups when iterating large portfolios.

### How do I add a new property to Jurny through Jentic?

Search Jentic for 'create a vacation rental property', load POST /properties, and execute with the address and configuration. Jentic returns the new property_id you can then use in reservation calls.

### Can I look up a guest's profile by ID?

Yes. GET `/guests/{guest_id}` returns the stored guest profile, which can be merged with reservation history from GET /reservations to populate a CRM record.

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

Yes. Jentic One runs self-hosted on your own infrastructure, so your rules decide which Jurny operations and credentials the agent may use. Because Jurny puts the property id in the URL path, such as GET `/properties/{property_id}`, you can pin the agent to a single property and let it read that record and nothing else. You choose the operations it may call, so write actions like POST /reservations or POST /properties stay off limits unless you explicitly add them.