# Guesty integrations: listings and reservations

> Create a listing, create a reservation and create a guest in Guesty, and start a workflow when Guesty sends “Reservation created”.

**Canonical page:** https://tray.ai/connectors/guesty-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Guesty is property management software for short-term rental companies, covering listings, reservations, guest messaging, owners and payments across booking channels. Tray.ai connects to Guesty through the HTTP Connector, so your workflows can call the Guesty API alongside the rest of your stack.

## Use cases

### Listings

Read, create, update, and delete listings in Guesty from any Tray.ai workflow. The Guesty API covers calls such as list listings and create a listing.

- List listings
- Create a listing
- Get a listing

### Reservations

Read, create, and update reservations in Guesty from any Tray.ai workflow. The Guesty API covers calls such as search reservations and create a reservation.

- Search reservations
- Create a reservation
- Update reservation status

### Guests

Read, create, and update guests in Guesty from any Tray.ai workflow. The Guesty API covers calls such as list guests and create a guest.

- List guests
- Create a guest
- Get a guest

### Conversations

Read and create conversations in Guesty from any Tray.ai workflow. The Guesty API covers calls such as list conversations and get a conversation.

- List conversations
- Get a conversation
- Send a message

### Owners

Read, create, update, and delete owners in Guesty from any Tray.ai workflow. The Guesty API covers calls such as list owners and create an owner.

- List owners
- Create an owner
- Update an owner

### Calendars

Read and update calendars in Guesty from any Tray.ai workflow. The Guesty API covers calls such as get a listing calendar and update a listing calendar.

- Get a listing calendar
- Update a listing calendar

## Challenges Tray.ai solves

### Keeping Guesty credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Guesty credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Guesty API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Guesty API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Guesty?

Yes. Tray.ai connects to Guesty through the HTTP Connector, which calls the Guesty API directly. Any call the Guesty API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Guesty?

The Guesty API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Guesty connector?

Guesty runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Guesty connector from the Guesty API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/
