The RentManager Web API (WAPI12) follows REST conventions; authenticate using an API key or username/password token exchange documented in the RentManager technical documentation PDF available from info.rentmanager.com.
To post a charge, send a POST request to the tenant charges endpoint: POST https://YOURCOMPANY.api.rentmanager.com/Tenants/{tenantId}/Charges with a JSON body specifying the charge type, amount, GL account, and due date.
To override the hard-close date restriction on historical postings, append the query parameter saveOptions=IgnoreHardClose to the charge POST request.
Record a payment by POSTing to the tenant payments endpoint with the payment amount, date, payment type (check, ACH, credit card), and a reference number.
Retrieve a tenant's ledger history (all charges, payments, credits) via the tenant ledger GET endpoint filtered by date range to reconcile balances.
Use GET on the outstanding balances resource at the portfolio level to identify all tenants with a balance due, suitable for batch collections workflows.
Known gotchas
The RentManager API base URL includes your company's subdomain (e.g., yourcompany.api.rentmanager.com); this varies per client installation and is provided during API onboarding.
Charge type IDs and GL account IDs are environment-specific integers configured in each RentManager database; you must look these up via the reference data endpoints before posting charges.
Posting payments without the correct bank account ID will cause the payment to appear undeposited; always retrieve the active bank account list and specify the target account in the payment body.
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