Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Your.Rentals Marketplace 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmarketplace.your.rentals%2Fyour-rentals-marketplace" | shStep 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%2Fmarketplace.your.rentals%2Fyour-rentals-marketplace" | 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.
What an agent can do with Your.Rentals Marketplace API.
List vacation rental bookings filtered by organization, integration, or date range for downstream sync
Register and revoke partner API keys scoped to a specific Your.Rentals organization
Subscribe Zapier-style webhooks to booking and listing events and replay deliveries
Map external channel listing IDs (Super-Adria, Passepartout, Oxygen) to Your.Rentals units
GET STARTED
Validate Zapier authentication tokens before triggering downstream automations
Update listing-level settings such as Oxygen pricing rules tied to specific units
Patterns agents use Your.Rentals Marketplace API for, with concrete tasks.
★ Channel Manager Booking Sync
Property managers using Your.Rentals alongside a channel manager need to pull reservations into their own PMS. The Marketplace API exposes booking-list endpoints scoped per organization and integration so partners can backfill historical reservations and incrementally sync new ones without polling each channel separately. Typical integrations cover the last 90 days of bookings and run nightly.
Call the Zapier bookings list endpoint for organization 'org_123' filtered to the last 7 days and return reservation IDs with check-in dates.
Partner Listing Mapping
When a Your.Rentals unit is also distributed via Super-Adria, Passepartout, or Oxygen, the partner's listing ID must be linked to the Your.Rentals unit so prices and availability sync correctly. The listing-mapping endpoints let integrators fetch existing mappings, attach a new external listing ID, and detach stale mappings during channel migrations.
List Passepartout listing mappings for organization 'org_123' and create a new mapping for unit 'unit_456' to external listing 'pp_789'.
Zapier Webhook Automations
Your.Rentals customers often automate operational workflows (cleaning crew dispatch, guest messaging, accounting) via Zapier. The webhook endpoints register subscription URLs that receive POST callbacks on booking events. Auth-validate is used in the Zapier connection test step so triggers fail fast when credentials are wrong.
Create a webhook subscription pointing to https://hooks.zapier.com/abc and verify the auth token validates against /zapier/auth/validate.
AI Agent Reservation Operations
An AI agent that manages a portfolio of short-term rentals can use Jentic to call Your.Rentals Marketplace operations on demand, such as fetching a booking by ID, updating Oxygen listing settings, or revoking an exposed API key. Jentic stores the bearer token in its vault and surfaces operations by intent, so the agent never sees the raw secret.
Search Jentic for 'list rental bookings', load the Your.Rentals operation schema, and execute it with organizationId 'org_123' to return today's check-ins.
15 endpoints — jentic publishes the only available openapi specification for your.
METHOD
PATH
DESCRIPTION
/zapier/actions/bookings/list
List bookings for a Zapier-connected organization
/zapier/webhooks
Subscribe a webhook to booking events
/zapier/webhooks/{id}
Remove a webhook subscription
/zapier/auth/organizations/{organizationId}/api-keys
Create a partner API key for an organization
/zapier/auth/validate
Validate a Zapier auth token
/organizations/{organizationId}/super-adria/{superAdriaIntegrationId}/units
List units exposed via Super-Adria
/zapier/actions/bookings/list
List bookings for a Zapier-connected organization
/zapier/webhooks
Subscribe a webhook to booking events
/zapier/webhooks/{id}
Remove a webhook subscription
/zapier/auth/organizations/{organizationId}/api-keys
Create a partner API key for an organization
/zapier/auth/validate
Validate a Zapier auth token
/organizations/{organizationId}/super-adria/{superAdriaIntegrationId}/units
List units exposed via Super-Adria
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Your.Rentals by hand means handling both its bearer token and X-API-Key Zapier key, learning the /zapier and /organizations paths, and managing webhook registration yourself. Through Jentic you install once, import the Your.Rentals Marketplace API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Your.Rentals puts the organization id in the URL path (/organizations/{organizationId}/...), so a rule can pin your agent to one organization: it can read that organization's units and nothing else. You choose the operations it may call, so destructive ones like deleting a webhook are not included unless you add them.
Credential isolation
Your Your.Rentals bearer token and Zapier key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list rental bookings' or 'register a booking webhook', and Jentic returns the matching Your.Rentals operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Your.Rentals Marketplace API through Jentic.
Why is there no official OpenAPI spec for Your.Rentals Marketplace API?
Your.Rentals does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Your.Rentals Marketplace 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 Your.Rentals Marketplace API use?
The API supports two schemes: HTTP bearer tokens for general access and an `X-API-Key` header for the Zapier integration surface. Through Jentic, both are stored encrypted in your Jentic One instance and the agent only ever receives a scoped session reference.
Can I list short-term rental bookings with the Your.Rentals Marketplace API?
Yes. The Zapier action endpoint `POST /zapier/actions/bookings/list` returns bookings for an organization, and the per-integration endpoints under `/organizations/{organizationId}/...` expose channel-specific reservation data.
What are the rate limits for the Your.Rentals Marketplace API?
Your.Rentals does not publish rate limits in the spec. Treat it as a partner API and apply conservative client-side throttling (1-2 requests per second per organization) until you have confirmed quotas with Your.Rentals support.
How do I sync a new booking event into my system through Jentic?
Use Jentic's search to find the operation with the query 'subscribe to rental bookings webhook'. Jentic loads the schema for `POST /zapier/webhooks`, then your agent executes it with the target URL. Install with `pip install jentic` and authenticate with your `JENTIC_AGENT_API_KEY`.
Can I map a Your.Rentals unit to an external Passepartout listing?
Yes. The endpoints under `/organizations/{organizationId}/passepartout/{integrationId}/listing-mappings/{listingId}` create, update, and remove the mapping between a Your.Rentals unit and a Passepartout listing ID.
Can I limit what my agent is allowed to do with the Your.Rentals Marketplace API?
Yes. Because you run Jentic One yourself, your own rules decide which Your.Rentals operations and credentials the agent can use. Since the organization id sits in the URL path (/organizations/{organizationId}/...), a rule can pin the agent to a single organization so it only reads that organization's bookings, units, and listing mappings. You also pick the exact operations it may call, so destructive ones like deleting a webhook subscription stay off the agent's list unless you explicitly add them.
Know of an official OpenAPI document? Contribute it →
For Agents
List and reconcile short-term rental bookings, manage Your.Rentals listing mappings across channel partners, and register webhooks that fire when reservations change.
Use for: Retrieve all bookings for a Your.Rentals organization in the last 30 days, I want to register a Zapier webhook that fires whenever a new reservation is created, Find all listing mappings between Your.Rentals units and Passepartout listing IDs, Set up a fresh API key for a partner organization and rotate the old one
Not supported: Does not handle guest messaging, payment capture, or property-cleaning workflows - use for booking sync, channel listing mapping, and partner webhook setup only.
Jentic publishes the only available OpenAPI specification for Your.Rentals Marketplace API, keeping it validated and agent-ready. Your.Rentals is an all-in-one operating platform for short-term rental managers covering distribution, listings, bookings, and channel integrations. The Marketplace API exposes the third-party integration surface used by partners such as Zapier, Super-Adria, Passepartout, and Oxygen, including listing mappings, booking lookups, webhook subscriptions, and organization-scoped API key management. It is intended for property managers and partner developers who need to push reservations, reconcile listings, or trigger workflows when bookings change.