Back to jobs

Rent Manager API Integration + AI Lease Abstraction (Phased)

Search - API Integration · notified · UID ~022089390483588562578

Open Job

Job Details

Budget Unknown
ExperienceExpert
DurationUnknown
Weekly hoursUnknown
Client countryUnknown
ProposalsUnknown
InterviewingUnknown
Invites sentUnknown
First seenMon, Aug 17, 2026 4:51 PM
Last seenTue, Aug 18, 2026 12:38 AM

Description

Summary # Rent Manager API Integration + AI Lease Abstraction (Phased) **Client:** Street Realty — commercial real estate firm (brokerage, property management, development/construction) based in Arlington, TX. **Engagement:** Fixed-price, phased. We want to award Phase 1 first and extend to later phases based on results. Please bid on Phase 1 and give a rough estimate for Phases 2 and 3. --- ## Background We manage a commercial portfolio in Rent Manager (Rent Manager Online). Two goals: 1. Surface live operational KPIs on an internal dashboard ("Street Live") displayed on office TVs. 2. Reduce the manual work of abstracting new and renewal leases into Rent Manager. We have an existing front-end dashboard already built. It reads a single JSON file and needs no changes — you are building the data pipeline behind it, not the display. We are a Microsoft 365 shop (SharePoint, Outlook, Power Automate available). --- ## Phase 1 — Read-only KPI pipeline **Scope** - Establish authenticated connection to the Rent Manager API (and/or Rent Manager Open Access — advise us which is appropriate for read-only reporting). - On a schedule (target: every 15 minutes), retrieve and compute: - Rent billed vs. collected, month to date - Delinquency total and count of delinquent tenants - Portfolio occupancy by square footage (leased SF / total SF) - Open work order count - Average work order response time - Average emergency response time - Upcoming lease expirations (next 90/180 days) - Write results to a single `board.json` file in a SharePoint document library, matching a schema we will provide. - Fail safely: if Rent Manager is unavailable, leave the last good file in place rather than writing a partial or empty file. Log failures somewhere we can see them. - Handle time zones correctly (we are US Central). **Deliverables** - Working scheduled integration in an environment we own (Azure Functions, Power Automate, or similar — propose what you recommend and why). - Credentials stored securely, never in client-side code or in the JSON output. - Written runbook:

Skills

API

Notification History

ChannelTypeStatusSentError
telegram ai_job_alert sent Mon, Aug 17, 2026 4:52 PM -
telegram pre_ai_job_alert sent Mon, Aug 17, 2026 4:52 PM -

User Actions

ActionActed at
No actions.