Changelog
Start typing to search…
Back to All

2026-03-24

March 24th, 2026

New feature for adding and managing external links in your property's "Channels" section, and a new owner-guest creation endpoint to support owner-guest reservations


Added

  • Add POST /properties-api/listing-settings/external-links/{propertyId} for adding an external link to the property's page
  • Add PUT /properties-api/listing-settings/external-links/{propertyId}/{linkId} for updating the URL and name of an existing external link
  • Add PUT /properties-api/listing-settings/external-links/{propertyId}/order for reordering the list of external links
  • Add GET /properties-api/listing-settings/external-links/{propertyId} for retrieving the property's list of external links
  • Add DEL properties-api/listing-settings/external-links/{propertyId}/{linkId} for deleting an external link
  • Add POST /owners/:ownerId/guest endpoint to support owner-guest reservations

Changed

  • Add EXPENSES_CSV_IMPORT as a filterable trigger to GET /accounting-api/journal-entries and GET /accounting-api/journal-entries/all
  • Document GET /expenses-api/expenses pagination limit as “up to 100 items per page” in the endpoint description.
  • Document POST /expenses-api/expenses validation/usage details in the endpoint description (including lock period behavior and clarifications around required inputs and mutual exclusivity of owners vs listingIds).
  • Document GET /expenses-api/expenses/:id} returned details to explicitly mention attachments in the endpoint description.
  • Document POST /expenses-api/expenses/:id/attachments constraints and required fields in the endpoint description (including “up to 10 attachments per request” and urlThumbnail).
  • Document DELETE /expenses-api/expenses/:id/attachments/:attachmentId behavior in the endpoint description to emphasize it returns the updated expense after removal.
  • Document updated cancellation rules for POST /expenses-api/expenses/:id/cancel in the endpoint description (expanded eligible statuses and clarified rejection conditions).
  • Simplify/standardize multiple 404 response descriptions (e.g., “Expense not found”, “Expense or attachment not found”).
  • Add businessInformation.businessName to Owner create/update payloads and expose it in Owner responses (POST /owners, PUT /owners/:ownerId, GET /owners/:ownerId).
  • Add ownersPortalSettings.rentalIncome to Owner create/update payloads and expose it in Owner responses (POST /owners, PUT /owners/:ownerId, GET /owners/:ownerId).
  • Add bulk support for businessInformation.businessName and ownersPortalSettings.rentalIncome in request/response items (POST /owners/bulk).

Resources