Property Management / Updated August 2026
Guide / By Rob Lowry, Founder of LaunchEngine
Leasing tool APIs: what you can actually build on RentEngine, Tenant Turner, and ShowMojo
Your leasing platform holds the data your operation runs on: prospects, showings, applications, lockbox events. Whether you can get it out programmatically varies a lot by vendor. We run a leasing integration in production, so here's the API-level comparison the marketing pages don't give you.
7 min read
| RentEngine | Tenant Turner | ShowMojo | |
|---|---|---|---|
| Docs | docs.rentengine.io, fully public | Customer portal (new API); partner docs public | docs.showmojo.com, public |
| Auth | JWT bearer tokens, self-service | API keys (customer + property level) | Documented per endpoint (v3) |
| Webhooks | Yes, retries with backoff | Not announced | Yes (leads and showings) |
| Cost | Included with platform | Included, all customers | Included |
| Status | v1.1.1, actively expanding | Updated July 2026 | v3 live, v4 in development |
Compiled August 12, 2026 from each vendor's documentation and announcements. Details change; verify with each vendor.
01 / RentEngine
The fully public one, and it's been growing fast
RentEngine publishes its complete API reference at docs.rentengine.io with no login wall, spanning 18 resource categories:
Mechanics: self-service JWT bearer tokens created in the developer portal (shown once, carrying the creating user's permissions), a staging environment alongside production, pagination capped at 100 records per page, and webhooks configured per data type with reliable delivery and exponential-backoff retries.
Worth noting for anyone who filed API wishlists with vendors before: in 2025 this API covered lockboxes, units, and webhooks, and the leasing-funnel data (prospects, showings, applications, calls) simply wasn't there. We know because we asked for it. It is now, which says something about the direction and the pace.
02 / Tenant Turner
Newly refreshed, documented behind the login
Tenant Turner shipped a meaningful API update in July 2026, free for every customer, covering applicant and pre-qualification data, showings, and feedback, the data an operations team actually wants out of a leasing tool. The company explicitly formatted the docs for AI coding agents as well as human developers, a sign of where they expect integrations to come from.
The practical caveats: the refreshed documentation lives inside the customer portal, so you can't scope the new API in full before you're a customer, and the announcement doesn't mention webhooks, so assume polling until they tell you otherwise. Auth is API-key based, with separate keys at the customer and property level.
There is public reference material if you know where to look, though. Tenant Turner's partner-facing API has circulated openly for years: the base URL is api.tenantturner.com with versioned endpoints (/v1/customers, plus a properties API keyed per customer), documented in partner docs and reflected in the community-maintained PHP SDK on GitHub, which links the original documentation. If you're scoping before signing, that SDK plus the July 2026 announcement is enough to understand the shape; the portal docs fill in the rest once you're in.
03 / ShowMojo
A working v3 today, a v4 on the way
ShowMojo documents its API publicly at docs.showmojo.com. The version you can build on today is the legacy v3, and it's listing-centric: import and update up to 100 listings per request with deduplication by address, code, or MLS ID, plus properties, report export, and webhooks for leads and showings. Zapier support covers the no-code cases.
The docs also show a v4 API marked as in active development as of August 2026. If you're starting a ShowMojo integration now, ask their team about v4 timelines before building deeply on v3, and note that under PropertyTek ownership the ShowMojo and Tenant Turner API roadmaps are worth asking about together.
04 / The use cases
What teams build with leasing APIs
- 01The leasing funnel, live in your ops workspace. Prospects, showings, and applications land on the boards where your team already coordinates renewals and turnovers. This is what our own RentEngine integration does: leasing stops being a separate silo you check and becomes rows your automations act on.
- 02Lockbox events as an audit trail. Access events from self-showing lockboxes, pulled or pushed via webhook, become a timeline: who entered which unit and when, matched against showings and turnover work.
- 03Listings pushed, not re-typed. ShowMojo's import API takes up to 100 listings per request with deduplication, and RentEngine syndicates from its own listing data, so vacancy marketing can flow straight from your PMS or ops boards without manual re-entry.
- 04Leasing KPIs next to operational ones. Speed-to-lease, show rate, and source attribution pulled from the API into the same dashboards as work-order aging and renewal rates. One scoreboard for the whole operation.
- 05After-hours coverage with a paper trail. Call and message records from RentEngine's API mean every AI-handled conversation is queryable: what was asked, what was promised, and what needs human follow-up in the morning.
05 / The build test
Could you ship a leasing dashboard on it?
Here's a concrete test that separates these APIs better than any feature list: could a third party, today, build a leasing reporting dashboard wired into a custom operations workspace? That takes five capabilities. Score each platform against its own documentation:
| Needed to build it | RentEngine | Tenant Turner | ShowMojo |
|---|---|---|---|
| Read the funnel (prospects, showings, applications) | Dedicated documented endpoints for each: Prospects, Showings, Rental Applications, Leasing Events | Added July 2026 (applicants, pre-qualification, showings, feedback); docs in portal | Leads and showings via v3 webhooks; no documented query endpoints for the funnel |
| Reporting-grade metrics | Reporting and Market Tool endpoint categories; days-on-market, unit health, and prospect benchmarks served via API | Leasing analytics exist in-app; no publicly documented API exposure | Report Export endpoints (batch files, not queryable metrics) |
| Real-time change signals (webhooks) | Configurable per data type, with retry delivery | Not announced | Lead and showing webhooks (v3) |
| Operational event data (calls, messages, lockbox events) | Documented endpoints for calls, messages, lockbox events and installations | No public documentation | No documented endpoints |
| Scopeable before you commit | Full public docs plus a staging environment | Partner docs and community SDK public; full new-API docs in customer portal | Public docs; v3 is legacy with v4 in development |
| A shipped third-party reporting dashboard | Yes: the monday.com integration (built by us; see disclosure) | None publicly documented that we could find | None publicly documented that we could find |
Scored August 2026 against each vendor's public documentation and announcements. "Not documented" means we could not find it publicly; vendors may offer more under partnership or in portal docs, so verify directly.
The conclusion falls out of the table rather than our opinion: RentEngine is the only one of the three where every layer of that dashboard is buildable from documented, publicly scoped interfaces today, queryable funnel data, reporting metrics, webhooks for freshness, and event-level records, and it's the only one with a shipped third-party reporting dashboard as an existence proof. That's what modular composability means in practice: the API is complete enough that your leasing platform can be one component in a stack you design, rather than a destination you log into.
Worth saying plainly for fairness: this picture is time-stamped. Until July 2026, Tenant Turner's publicly documented surface was customers and properties, so a funnel-level dashboard simply wasn't buildable from documented interfaces; the new API adds the right data domains, and if webhooks and reporting endpoints follow, this table changes. ShowMojo's v4 could do the same. We'll update this guide as they ship.
06 / Build vs. buy
Putting leasing data to work
The buy option
We already built the RentEngine side
LaunchEngine's RentEngine integration runs on this exact API: units, lockboxes, and leasing data synced into monday.com boards where your operations already live. Disclosure: we sell this integration, so weigh our enthusiasm for RentEngine's API accordingly; the facts above are checkable either way.
Building something custom?
Get a Leasing API Review before you commit the architecture
Scoping a build against any of these APIs? Bring your plan to a 30-minute working session: which platform's API fits your workflow, webhook versus polling design, and how leasing data should land in your ops stack.
About this guide
This guide is for informational purposes only and does not constitute financial, legal, or business advice. API details are compiled as of August 2026 from each vendor's public documentation and announcements, plus LaunchEngine's own integration experience, and may change; verify capabilities with each vendor. Disclosure: LaunchEngine sells a RentEngine-to-monday.com integration; no vendor paid for inclusion in this guide. All trademarks belong to their owners; this guide is not authored, reviewed, or endorsed by any vendor mentioned. Spot an error? Email rob@launchengine.com and we'll correct it.
FAQ
Common questions about leasing platform APIs.
Want your leasing funnel in your ops workspace?
Book 30 minutes and we'll show a live leasing-to-operations flow, or review the custom build you're planning.