---
title: Guesty credentials and what each one accesses
description: "HomeRunner needs two credential sets from Guesty, plus one payment key if you charge through Stripe. 1. **Open API credentials** (an OAuth application…"
url: "https://homerunner.io/docs/what-guesty-credentials-does-homerunner-need-and-what-does-each-one-access/"
updated: "2026-10-26"
category: PMS connections and sync
---

# Guesty credentials and what each one accesses

HomeRunner needs two credential sets from Guesty, plus one payment key if you charge through Stripe.

1. **Open API credentials** (an OAuth application created at Guesty's integrations page): these sync listing content to your website, including titles, descriptions, photos, amenities, and tags. HomeRunner reads listing data, with one exception: when the most-booked-property feature is enabled, HomeRunner updates the listing's tags.
2. **Booking Engine API key** (client ID and secret): this serves quotes and availability for the properties enabled on that key.
3. **Stripe publishable key** (only if your account charges through Stripe): this powers the card form at checkout. Accounts on Guesty Pay do not need this step.

**What HomeRunner writes to Guesty.** When a booking comes in through your website, HomeRunner creates the reservation, with its custom fields and payment record, and attaches the guest's payment method. HomeRunner also registers the webhooks it listens to.

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