---
title: Restricting the Guesty Booking Engine API key
description: "You can restrict your Guesty Booking Engine API key to specific properties, and HomeRunner works with a restricted key. **How the key limits your…"
url: "https://homerunner.io/docs/can-i-restrict-my-guesty-booking-engine-api-key-to-specific-properties-for-my-ho/"
updated: "2026-10-26"
category: PMS connections and sync
---

# Restricting the Guesty Booking Engine API key

You can restrict your Guesty Booking Engine API key to specific properties, and HomeRunner works with a restricted key.

**How the key limits your import.** HomeRunner's Guesty sync enumerates properties through the Booking Engine API, so the property list configured inside the key defines every listing HomeRunner can import. Any property left out of the key can never reach HomeRunner, which makes the key the hard boundary. Tag-based filtering still applies on top of the key as a second, independent filter, and you can use both together.

**Creating the key.** In Guesty, create the key under **Integrations > Online Booking Solutions > Booking Engine API**, and set the booking options to **Both**.

**Adding properties later.** If you add properties later, update the key's property list first. A listing outside the key cannot sync no matter how it is tagged.

**Open API credentials.** The Booking Engine key is one of two credential sets your HomeRunner Guesty connection needs. You also need Open API credentials, created as an OAuth application at app.guesty.com/integrations/oauth-apps. Guesty does not offer a property-selection step on OAuth applications, so that credential is account-level by design. Your import scope is still controlled by the Booking Engine key and tags.

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