What's New in v0.1.22: Tenant Portal API Routes

We've shipped the Next.js API route layer for the tenant portal — covering both active tenants and prospect tenants. This is a foundational release that connects the myProp portal to real-time AgentOS data for the most common tenant journeys.

Two Tenant Experiences, Purpose-Built

myProp recognises that a tenant mid-tenancy has very different needs from someone who is still searching. v0.1.22 reflects that with two separate sets of API routes, each shaped around the relevant data and actions for that stage.

Active Tenants

For tenants already in a property, the new active tenant route bundles tenancy data into a single response. Rather than making multiple round-trips to AgentOS, the portal fetches everything needed for the tenancy dashboard in one call — keeping the experience fast and cohesive.

Prospect Tenants

The prospect journey is more involved, so it gets more routes:

Pre-fill data means applicants don't have to re-enter information they've already provided — the portal retrieves it and populates forms automatically.
Advertised properties surfaces live listings from the agency, so prospects see current availability.
Preferences lets the portal personalise the experience based on what the prospect is looking for.
Viewing scheduling closes the loop by letting prospects book viewings without picking up the phone.

What This Enables

With these API routes in place, the tenant portal can now:

Show an active tenant their tenancy details from AgentOS in real time.
Guide a prospect from browsing available properties through to scheduling a viewing and submitting an application — all within the portal.

Under the Hood

All routes are built as standard Next.js API routes and sit in front of the AgentOS (letmc.com) API. They handle the authentication and data-shaping layer, returning clean, portal-ready responses to the client UI.

Released as part of myProp v0.1.22.