Retrieve Guesty property owner records, owner documents, and associated reservations via the Open API
domain: open-api-docs.guesty.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to the Guesty Open API with the OAuth2 client-credentials flow.
List owners with GET /owners using skip, limit, sort, and a filter expression, or fetch a single owner by id.
Pull owner-linked reservations via the owners-reservations endpoints to build owner-facing reporting.
Retrieve a specific owner document with GET /owners/{ownerId}/documents/{documentId} when you need files tied to an owner.
For financial updates, use the documented accounting endpoint PUT /v1/accounting-api/owners/{id}/working-capital; PUT /owners-reservations/{id} is also available for owner-reservation records.
Known gotchas
There is no documented general-purpose owner-profile update endpoint - do not assume PUT /owners/{id} exists; documented owner-scoped PUTs are the accounting working-capital endpoint and PUT /owners-reservations/{id}.
Some legacy top-level fields on the owner object are deprecated in favor of the newer owners-portal-settings structure - use the newer structure.
Owner-facing document and reservation data can lag the PMS UI; confirm behavior in a sandbox account before production use.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?