Skip to content

MyRentalCalendar Developers

Build on the PMS your agency already runs on. One key format, three doors — for the agency, for its landlords and for its cleaning companies — over REST, and straight into AI agents via MCP.

Agency API

The whole agency: units, availability, live quotes and the rate calendar, bookings, guests, enquiries, tasks, invoices and payments, security deposits, housekeeping jobs, landlords and running costs. Keys are created in the agency console. Reference →

Landlord API

One landlord’s slice, for their accountant or their own tools: their units, anonymised occupancy, statement and payouts, running costs, documents and the conversation with the office. Keys are created in the landlord portal and are bound to that landlord. Reference →

Cleaning API

One crew’s work, for a cleaning company’s dispatch software: units, derived jobs with windows and deadlines, the day route, start and finish reports. Keys are created in the cleaning portal and are bound to that crew. Reference →

One key format, explicit scopes

Every key is hr_live_…, shown once, hashed at rest, revocable instantly. Scopes decide what a key may do; the door it was made for decides what it may see at all. The agency sees and can revoke every key of every door.

Real prices, not estimates

POST /partner/v1/quote runs the agency’s actual pricing engine — seasonal rates, cleaning fee, VAT, Tourism Dirham, active promotions. What the API quotes is what the website charges and what the invoice carries.

AI-agent ready

Point Claude (or any MCP client) at https://api.myrentalcalendar.com/mcp with an agency key and your assistant can check availability and price stays with live data.

Privacy by construction

Guest personal data needs its own scope on the agency door and does not exist on the other two. Identity documents never leave the PMS through any API. Landlords see dates and money, cleaners see rooms and times.