---
title: Guesty Open API and Booking Engine API
description: HomeRunner uses two separate Guesty integrations. Each has its own client ID and secret, created in your Guesty account. Both are required because they…
url: "https://homerunner.io/docs/which-guesty-integrations-does-homerunner-require-and-what-is-the-difference-bet/"
updated: "2026-10-26"
category: PMS connections and sync
---

# Guesty Open API and Booking Engine API

HomeRunner uses two separate Guesty integrations. Each has its own client ID and secret, created in your Guesty account. Both are required because they serve different functions and supplement each other.

**Open API application.** The Open API application (host: open-api.guesty.com) is created under **Guesty > Integrations > Developer tools**. It handles property details, calendars, reservations, and payment records. Its name is internal to Guesty and never appears on Google or your website.

HomeRunner calls these Open API endpoints: GET v1/accounts/me; GET v1/accounts/me/custom-fields; GET v1/listings; GET v1/listings/{listingId}; PUT v1/listings/{listingId} (tags); GET v1/listings/{listingId}/custom-fields; GET v1/marketing/fields/{listingId}; GET v1/properties/house-rules/unit-type/{listingId}; GET pricingrules/{listingId}; GET v1/availability-pricing/api/calendar/listings/{listingId}; GET v1/additional-fees/account; GET v1/additional-fees/listing/{listingId}; GET v1/reviews; GET v1/reservations; GET v1/reservations/{reservationId}; POST v1/reservations; PUT v1/reservations/{reservationId} (cancel); POST v1/reservations/{reservationId}/payments; PUT v1/reservations/{reservationId}/payments/{paymentId}; GET v1/guests-crud/{guestId}; GET v1/guests/{guestId}/payment-methods; POST v1/guests/{guestId}/payment-methods; GET v1/payment-providers/stats; GET v1/payment-providers/{providerId}; GET v1/payment-providers/provider-by-listing; GET and POST v1/webhooks; DELETE v1/webhooks/{id}.

**Booking Engine API.** The Booking Engine API (host: booking.guesty.com) is created under **Guesty > Marketing and sales > Distribution > Guesty Booking Engine API**. It powers availability search, itemized quotes for selected dates, and instant booking on your website. It is also the connection Google Vacation Rentals reads when displaying your listings. Google displays the name of this key on the listing, so name it after your brand.

HomeRunner calls these Booking Engine endpoints: GET api/listings; GET api/listings/{listingId}; POST api/reservations/quotes; GET api/reservations/quotes/{quoteId}; POST api/reservations/quotes/{quoteId}/coupons; POST api/reservations/upsell/{quoteId}; POST api/reservations/quotes/{quoteId}/instant; POST api/reservations/quotes/{quoteId}/inquiry; POST api/reservations; GET and PUT api/metasearch/pointofsale/google/config.

**Endpoint without credentials.** One additional endpoint is called without credentials: GET app.guesty.com/api/pm-websites-backend/listings/{listingId}/calendar.

Still stuck? [Contact the HomeRunner team](https://homerunner.io/contact/) with your site address and what you tried, and we take it from there.