Changelog
Back to All

2026-08-12

August 12th, 2026

Added

  • Add PATCH /business-models-api/light-business-models/{id} endpoint to partially update a Business Model — currently supports only the category field, creating a new version without requiring the full payload

Changed

  • GET /business-models-api/light-business-models gains an optional includeAssignedListings query param; when true, the response includes a new assignedListings array (listingId, assignmentType, assignedAt, activationDate, sorted by assignedAt descending and capped at 1000) plus an assignedListingsTruncated boolean, and always gains a new required category field
  • POST /business-models-api/transactions/expenses description now documents the PMC/owner expenseShare split behavior (defaults to 100% PMC); now documents a 404 response for an unknown business model
  • POST /business-models-api/transactions/expenses-by-listing — same expenseShare split clarification and new 404 response for an unknown business model
  • POST /business-models-api/transactions/owner-charges response VAT category gains a categoryName field; now documents a 404 response for an unknown business model
  • POST /business-models-api/transactions/owner-charges-by-listing — same VAT categoryName field and new 404 response for an unknown business model
  • GET /owner-statement-api/owner-statements gains six new optional filter query params — status, sharedVia, listingId, businessModelId, generatedAtFrom, generatedAtTo — and response items gain new required table-parity fields listings, businessModels, minimumAccountBalance, sharedVia, generatedAt, status; pdfDownloadUrl description now also covers the not-yet-generated case; the 400 response now documents validation failures for the new filters (invalid status/sharedVia enum values, invalid listingId/businessModelId, inverted generatedAtFrom/generatedAtTo)
  • POST /taxes and PATCH /taxes/{id} request bodies: type field description rewritten to state that multiple taxes of the same type are allowed on the same account/listing (each a distinct entity with a distinct name), replacing the old "each tax type can only be defined once" wording — with the added constraints that same-type taxes must all share the same inclusive/exclusive setting, and multiple inclusive taxes of the same type are only allowed if their appliedOnFees don't overlap and none sets appliedToAllFees: true
  • isInclusive field gains a description (previously undocumented type-only field), affecting POST /taxes, PATCH /taxes/{id}, GET /taxes/account, GET /taxes/unit-type/{id}, and GET /taxes/unit-type/{id}/actual — explains that true folds the tax into the accommodation fare rather than adding it on top, and that it can't be combined with isAppliedByDefault, appliedByDefaultOnChannels, or conditionalOverrides