Hospitable opens owner statements to its API and MCP, including marking them paid

Hospitable has pushed owner statements out to its public API and its MCP server, which means the month-end work a property manager does by hand can now be driven by code, or asked for in plain English by an AI client.

The changelog post went up this month. The expansion itself took effect on 11 August, so this has been live for weeks without much notice.

What you can now do without touching the interface

Publish and unpublish an owner statement, and mark it paid or unpaid.

Create, view, update and delete expense and reimbursement transactions.

Retrieve owner statement business details.

Check the status of an owner portal invitation and whether an owner has connected a bank account.

Subscribe to owner statement and transaction events through webhooks.

Hospitable also added owner statement transaction line items, carrying expense and reimbursement detail that matches the Transactions table in the product, so what you pull through the API lines up with what you see on screen.

All of it requires a Mogul plan and the relevant permissions.

Why the webhooks are the real unlock

Most managers running owner accounting keep two sources of truth: the PMS and whatever they actually file from, usually Xero, QuickBooks or a spreadsheet that has outlived three staff members. Reconciling them is a monthly chore done from memory.

Webhooks on statement and transaction events change the shape of that. Instead of logging in to check whether October's statements went out and which owners have been paid, your accounting system gets told. Expense capture can run the other way too: a cleaner's invoice lands in your ops tool, your code writes the expense transaction, and it appears on the statement without anyone retyping it.

The owner portal invitation and bank connection status endpoints are smaller but solve a nagging problem. Chasing owners to finish onboarding is a job somebody does by opening each owner record one at a time. Now you can list who has not finished.

The part worth thinking about before you enable it

MCP and the public API get the same capabilities here, and that is not a neutral detail. An MCP server lets an AI assistant call these functions from a conversational request. "Mark September's statements as paid" is a sentence, and now it is also an action that moves money in your books.

Marking a statement paid when it is not, or deleting a reimbursement transaction, is the kind of mistake that surfaces weeks later in an owner's complaint rather than immediately on screen. Hospitable's note that permissions apply is the control, so use it: give an AI client a key scoped to what it genuinely needs, and keep write access to statement payment status away from anything with a loose prompt attached.

The Mogul gate also narrows who this is for. If you are on a lower plan and managing owner statements by hand, nothing here is available to you yet.

Where this sits

This is the third Hospitable change in a month to run through MCP, after the server gained smart lock control and calendar notes. The pattern is consistent: Hospitable is treating MCP as a first-class interface rather than a demo, and shipping the same capability to code and to AI clients at the same time.

For managers with any development capacity, owner accounting is now the most automatable part of Hospitable. For everyone else, the useful read is that it is coming, and your plan tier decides when.