2026-11-19
November 19th, 2026
Covers changes published between 6 and 18 November 2026; nothing in this release is breaking.
Changed
- Update the Reservation migration guide: legacy guest payment resources now retire on 1 March 2027, the same date as the legacy reservation endpoints (previously no removal date);
GET /reservations-v3/searchsupports incremental sync throughfilter[lastUpdatedAt](previously "not supported");POST /reservations.csvnamesGET /reservations-reports/{viewId}/csvas its first replacement; add "Who is this for?" and "Known constraints" sections - Rename the
Accounting (only available for accounting add-on users)group to[Add-on] Accounting(the/accounting-api/*and/business-models-api/*operations in it) andExpenses (only available for accounting add-on users)to[Add-on] Expenses(the/expenses-api/expenses*operations) - Add the paid add-on notice to the description of the 8
/accounting-api/*, 6/expenses-api/expenses*and 7/business-models-api/*operations in the two add-on groups; forGET /expenses-api/expenses,GET /expenses-api/expenses/{id},POST /expenses-api/expenses/{id}/cancel,DELETE /expenses-api/expenses/{id}/attachments/{attachmentId}andPUT /business-models-api/assignment/{businessModelId}this is the only change - Describe each field of the error responses of the 8
/accounting-api/*operations,POST /expenses-api/expensesandPOST /expenses-api/expenses/{id}/attachments - Rewrite
GET /accounting-api/reservations/{reservationId}/balancedescription, describe its response fields, document a 400 for a listing whose business model isn't active, and rename the path parameter from{id}to{reservationId}(it's a placeholder) - Rename the path parameter from
{id}onGET /accounting-api/owners/{ownerId}/working-capitalandPUT /accounting-api/owners/{ownerId}/working-capitalto{ownerId}, rewrite the GET description, and state that PUT replaces the current value, is idempotent, and can return a documented 404 - Rename the path parameter from
{id}onGET /accounting-api/disbursements/{disbursementId}to{disbursementsId}, change its summary to "Get disbursement by ID", and describe its response fields - Document accepted
payoutStatusandpayoutMethodvalues, addformatto the date parameters, and describe response fields onGET /accounting-api/disbursements - Rename
GET /accounting-api/journal-entriesto "Search recognized journal entries", rewrite its description, add@gt,@gteand@lteto thetransactionDateoperators, and state theskip,limitandsortByDatedefaults - Rename
GET /accounting-api/journal-entries/allto "Search all journal entries", apply the same documentation updates asGET /accounting-api/journal-entries, document thatrecognizedacceptstrueorfalse(case-insensitive), and add a requiredcategoryfield to response items - Rename
GET /accounting-api/categoriesto "List categories", rewrite its description (predefined and user-created categories, sorted A to Z), and describe its response fields - Document the PDF and image rules for
attachmentsonPOST /expenses-api/expenses(requiredurl,urlThumbnail,extension, andfileName; accepted extensions listed), change thefileNameexample toinvoice-copy.png, and note that PDFs added through the Open API can't be previewed in the Guesty dashboard - Apply the same attachment documentation, plus the "up to 10 attachments" wording, to
POST /expenses-api/expenses/{id}/attachments - Describe
listingsCount(current and scheduled future assignments, never capped) onGET /business-models-api/light-business-modelsand reword itsassignedListingsdescriptions - Describe
listingsCountand the 400 body fields onPATCH /business-models-api/light-business-models/{id} - Document that
vatOCConfig.categoryIdtakes precedence overcategoryCodeonPOST /business-models-api/transactions/owner-chargesandPOST /business-models-api/transactions/owner-charges-by-listing - Rewrite
POST /business-models-api/transactions/expenses-by-listingdescription: the listing comes fromexpenseShare.listingId, omittingexpenseSharerecords the expense on the PMC alone, andshareSplitof0keeps the full amount on the PMC while attaching the listing
Added
- Add
GET /expenses-api/expense-rulesendpoint to list recurring expense rules, filterable bystatus,listingId,categoryId,vendorId, andname; returns onlyactiveanddraftrules by default - Add
POST /expenses-api/expense-rulesendpoint to create a recurring expense rule (draftoractive) and assign it to listings; assignment is asynchronous, soGET /expenses-api/expense-rules/{id}reflects the listings once processed - Add
GET /expenses-api/expense-rules/{id}endpoint to retrieve a recurring expense rule, including itschargeable,share,vendor,channels, andtaxgroups and itslistingIds - Add bulk lookup (
filter[reservationId]andfilter[reservationId][in], up to 100 IDs), incremental sync (filter[lastUpdatedAt][gte],filter[lastUpdatedAt][lt]andsort=lastUpdatedAt) and alastUpdatedAtresult field toGET /reservations-v3/search, and document the new 400 cases - Document the
reservation.payments.updatedwebhook in the Payment webhooks guide: when it is sent (including when onlytotalPaymentFeeschanges) and its payload - Document in the Financial webhooks guide that the
guest-folio.updatedpayload has nototalPaymentFeesand that fee changes may not trigger it; subscribe toreservation.payments.updatedinstead
Fixed
- Correct the 403 ("Accounting feature flow disabled", previously "You do not have sufficient permissions to access this resource") and 404 ("Can't find the reservation or its listing's business model", previously "Can't find reservation, by provided ID") of
GET /accounting-api/reservations/{reservationId}/balance - Correct
GET /accounting-api/owners/{ownerId}/working-capital404 to "Owner was not found." (previously "Can't find owner, by provided ID") and documentworkingCapitalas required onPUT /accounting-api/owners/{ownerId}/working-capital(previously optional) - Type
skipandlimitasinteger(previouslynumber) onGET /accounting-api/disbursements,GET /accounting-api/journal-entries,GET /accounting-api/journal-entries/allandGET /accounting-api/categories - Correct
GET /accounting-api/journal-entriesandGET /accounting-api/journal-entries/all:limitminimum is 1 (previously 0),ledgeraddsPOAandDO(both deprecated),triggersaddsCOMMISSION_ADJUSTMENT,OPENAPI,EXPENSES_CSV_IMPORTandBULK_UPLOADS,datehasformat: date, and the guest, vendor, owner, listing, and charge-code response fields are nullable - Remove
assignedListingsandassignedListingsTruncatedfrom the 200 response ofPATCH /business-models-api/light-business-models/{id}(previously shown, though the operation has noincludeAssignedListingsparameter), and correct its 400dataexample to["Category must not exceed 255 characters"](previously thelistingIdsmessages from the assignment endpoint) - Correct the 404 of
POST /business-models-api/transactions/owner-charges,POST /business-models-api/transactions/owner-charges-by-listing,POST /business-models-api/transactions/expensesandPOST /business-models-api/transactions/expenses-by-listingto name the owner, listing, or vendor not found in a requireddatastring (previously onlymessageandstatus, with the messageCan't find business-model with ID {business_model_id})