Enable the Rent Manager Web API (WAPI12) in your Rent Manager Online account settings and obtain your authentication credentials
Authenticate using a POST to the /Authentication endpoint with your username and password to receive a session token for subsequent requests
Query properties using GET /Properties, units using GET /Units, and tenants using GET /Tenants; use the Filters query parameter for field-level filtering (e.g., Filters=PropertyID,eq,123)
Retrieve lease and financial data via GET /Leases and GET /Transactions; use the embed parameter to include related entities (e.g., embed=Tenant) in a single response
Write new records or updates using POST/PUT on the corresponding resource endpoints; the API follows RESTful conventions with resource names matching Rent Manager entity names
For available third-party integrations, use the Integrations tab within Rent Manager Online to activate pre-built connectors rather than building custom integrations from scratch
Known gotchas
WAPI12 is designed for Rent Manager Online (cloud-hosted); on-premise Rent Manager installations may use a different API version or have different connectivity requirements
Session tokens expire and must be refreshed; implement token lifecycle management rather than assuming a token obtained at startup will remain valid
The Filters parameter syntax is positional (fieldName, operator, value) rather than OData-style — use the official technical documentation PDF for correct syntax rather than inferring from other APIs
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp