POST /expenses-api/expenses/{id}/attachments - Upload attachments to existing expensesattachments field to:
POST /expenses-api/expenses - Include attachments when creating expensesGET /expenses-api/expenses and GET /expenses-api/expenses/{id} - View attachments associated with expensestaxPayeeTypes field to:
POST /expenses-api/expenses - Specify tax payee types when creating expensesGET /expenses-api/expenses and GET /expenses-api/expenses/{id} - View tax payee types associated with expensestype field in POST /expenses-api/expenses is now optional, providing greater flexibility when creating expensesVATPE (VAT on expense), MARF(markup on fees), and JE (manual journal entry) have been added to the chargeCode enum parameter of the /accounting-api/ endpoints.Added maximum length validations to POST /expenses-api/expenses request properties:
currency: 3 characters maximumname: 255 characters maximumdescription: 255 characters maximumtaxName: 255 characters maximumtaxDescription: 255 characters maximumImportant: Please ensure your client applications respect these field length restrictions before upgrading. Requests exceeding these limits will be rejected.
Due to a glitch in our publishing process, change logs weren't published as expected. Here are the Open API updates that have occurred in 2025.
url of an existing webhook; it was causing a bug. Editing eventsis still supported. Consider a delete and replace approach moving forward.calendar.updated.v2 to the list of supported webhook event enums. See the migration article for more information.includePaymentsTemplate is included in the query. Applies to:
GET /reservations-v3 response:
channelsSyncState: Channel reservation synchronization state.guestPreferences: Guest preferences captured during booking.preApproveState: Pre-approval status for inquiry reservations.ratePlans: Provides complete rate plan information, including pricing, cancellation policies, and applied promotions. An improvement on ratePlan.POST /reservations-v3 endpoints:
cleaningFee: You can now specify the cleaning fee on a quick booking.preferredLanguage: Add a preferred language to a guest's details at booking.accommodationFare field for setting a custom value to the quote creation endpoint.categoryId field has been added alongside the existing category field, which has also been updated to be optional instead of required. A gst enum has been added to the category options.activeLanguages parameter from a boolean value to a string array on the [Beta] upsert supported languages for specific listing endpoint.conditions) to the additional fees endpoints, as well as new fields to support versions 2 and 3 of this feature, where each fee is configured per channel (channelConfigurations) and manual source (sourcesConfigurations). Endpoints include:
[2025-03-20] new reservation reports API. It's built on Guesty's latest infrastructure. You can still pull reports using the legacy endpoint.
[2025-03-20] Owner portal settings added to owners:
showOverallGuestRating (boolean)showGuestReviews (boolean)inquiriesCount (boolean)averageBookingValue (boolean)averageGuestStay (boolean)ownerReservationRevenueLoss (boolean)ownerReservationBookedNights (boolean)[2025-03-20] Added explicit limit information to the Stripe payment processor listing assignment endpoint. The documentation now clearly states that a single request can process a maximum of 100 listing IDs. This allows you to design your integration with suitable batching logic from the beginning.
[2025-03-12] Add an indication that a shared space is shown on the channels as a living room on the following Spaces API endpoints: Add space to unit-type (Create Space), List room-types, and Edit space details.
[2025-03-11] Added error response schema to the Get calendar block logs document.
[2025-03-04] Added EPF to the invoice normal types table and added COMMISSION_CHARGE, DAMAGE_CHARGE, EQUIPMENT_RENTAL, GOLF_CART_RENTAL, HOMEOWNERS_ASSOCIATION, and RESERVATION_FEE to the predefined additional fees table.
[2025-03-03] Added deprecation notice to the Create a reservation endpoint. You should replace the booking flows based on that endpoint with the v3 flow.
[2025-03-03] Added owner dashboard settings fields to the Update owner in preparation for the new owners' dashboard in development.
| New field | Description | HC article |
|---|---|---|
netAccommodationFare (boolean) | When toggled on, the owner will view the net accommodation fare under the reservation tooltip only. Supported only for non-accounting users. | |
guestsReportsViewId (string) | Add a pre-defined reservation report to owners (BETA) | |
showReservationTooltips (boolean) | When toggled on the owner can view the data per reservation | |
showNotesForCoOwnerReservations (boolean) | When enabled, the owner can view notes entered for co-owner reservations, only available for new type owner reservations | |
netRentalIncome (boolean) | This toggle is available for Accounting users only. Allows your property owner to view rental income by hovering over a specific reservation to view the Reservation tooltip in the "My Properties" section. |
listing.removed webhook functionality. Added the event to the webhooks overview and listing webhooks guides.Property Photos[Beta]
You can now manage photos on your listings more effectively with a dedicated API. Check it out at the links below.
Marketing Fields
As an alternative to the UI interactions, two new endpoints have been created to provide you with the same functionality available on the UI. These endpoints are:
New Guide
cta/ctd fields have been added to the Update Calendars for Multiple Listings endpoint.New Guides
Guides
referenceId field to the Create owner charge and Create expense endpoints. This allows you to link the vendor reference ID with the charge or expense, group transactions on the owners' statement using the vendor's ID, and create an audit trail to the relevant vendor account or service.Upsells[beta]
Fee Types
GUESTY_BASIC_TRAVEL_COVERAGE and GUESTY_EXTENDED_TRAVEL_COVERAGE as additional fee types.
prices.monthlyPriceFactor and prices.weeklyPriceFactor parameters to the Create a listing listing document, clarifying the range and format of accepted values.assigneeId, listingId, reservationId, and supervisorId descriptions on the Create a new task and Update a task endpoints.
assigneeId - "The unique Guesty identifier of the person assigned to the task." Replaces, “The unique identifier of the person assigned to the task.”listingId - "The object ID of the Guesty listing the task is attached to." Replaces, “The object ID of the listing the task is attached to."reservationId - "The object ID of the Guesty reservation the task is attached to." Replaces, “The reservation ID of the listing the task is attached to."supervisorId - "The unique Guesty identifier of the person assigned to supervise the task." Replaces, "The uniqueID of the person assigned to supervise the task."blockReason field to the Update the calendar for a single listing endpoint. You can select from: Owner block, Offboarded, Migrated unit block, Maintenance, Onboarding, Emergency out of order, Do not sell, Deactivated, or Other.cta/ctd values could be updated, but this isn't the case. These body parameters were removed from the document.Available Endpoints
Guesty has replaced the property identifiers unitType and unitTypeId with the more familiar listing and listingId. The changes ensure consistency in naming conventions and improve code readability and maintainability. For example:
Before
curl 'https://open-api.guesty.com/v1/rm-los-calendar-service/unitType/{unitTypeId}/calendar?startDate=YYYY-MM-DD&endDate=YYYY-MM-DD&limit=100&skip=0' \
--header 'Accept: application/json'After
curl --globoff 'https://open-api.guesty.com/v1/rm-los-calendar-service/listing/{listingId}/calendar?startDate=YYYY-MM-DD&endDate=YYYY-MM-DD&limit=100&skip=0' \
--header 'accept: application/json'In addition, parameter and endpoint descriptions were updated to remove any ambiguity and increase understanding.
Resources
Reservation guest invoice items now have their own API and currently only support one action: adding an invoice item to an existing reservation. The table below highlights the changes between the versions.
| Status | Endpoint |
|---|---|
| ⚠️ Deprecated | /reservations/{id}/invoiceItems |
| ➕ Added | /invoice-items/reservation/{reservationId} |
curl --request POST \
--url https://open-api.guesty.com/v1/reservations/{reservationId}/invoiceItems \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '
{
"title": "Management Fee",
"amount": 100,
"normalType": "AFE",
"description": "Management fee description",
"secondIdentifier": "MANAGEMENT"
}
'Please note that realizationDates is a new optional body parameter for accounting customers only.
curl --request POST \
--url https://open-api.guesty.com/v1/invoice-items/reservation/{reservationId} \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '
{
"normalType": "AFE",
"title": "Management Fee",
"amount": 100,
"description": "Management fee description",
"secondIdentifier": "MANAGEMENT",
"realizationDates": [
{
"date": "2024-03-02"
}
]
}
'Working Capital is moving from the owners domain to accounting.
Working Capital now has its own API. This will allow you to update Owner Working Capital via the API and permit accounting role permission changes to be applied to Working Capital. Additionally, it opens the possibility of adding historical snapshots of its value.
The default behavior remains the same. When a new owner is added, their working capital remains at zero until it is updated.
We plan to deprecate Working Capital from the Owners API between February 26 and March 4, 2024 (UTC+2). Please ensure you update your flows beforehand.