Who can connect to your property software?

What this comparison covers

These reviews assess the named property-management products through their documented API, partner, data-delivery and customization routes. Some capabilities require paid add-ons (their commercial barriers cap the data-access score relative to the lowest paid plan). The grade does not imply that every capability is included on that plan.

MRI’s UK PMX exit disclosure does not establish US contract rights. RentCafe partner terms do not establish Voyager customer termination rights. Each vendor review identifies the product, route, region and agreement supporting its answers; rights on one route do not transfer to another.

We apply the site-wide customer-control methodology. The industry determines which products and routes we research; the grading questions, anchors and weights stay the same.

SAME QUESTIONS / DIFFERENT ROUTES

Vendor comparison

Overall grades combine six dimensions, with every answer retaining its route and plan (completeness and reliability still require live tests).

* Scores with unresolved inputs show the midpoint of their possible scores (document-based assessment). Scoring method ↗

Data access combines read, bulk delivery and query capabilities, capped by the access cost barrier. Paid add-ons and plan upgrades cannot earn the same access grade as access included on the lowest paid plan. Comparable activation times remain unresolved. See the formula ↗

PUBLIC AGREEMENTS / PROGRAM RULES

What are the actual conditions?

These are yes/no answers, defined categories and quantities from provider materials. A hyphen leaves an unresolved answer blank; hover for the research state and open the source for its conditions.

40 documented answers from 19 provider sources, checked 09 Oct 2026. Public terms describe the named route; signed customer agreements may differ. No tenant was tested.

ACCESS IS ROUTE-SPECIFIC

An API isn’t one access model

Customer credentials

A customer account can authorize a connection, but the plan must include the required objects and operations. AppFolio’s profile separates customer API entitlement from Stack partnership; the customer’s tier and the integration provider’s arrangement both need checking.

Approved partner interfaces

Yardi and Entrata document partner paths. Review requirements, contracts and licensed methods affect whether a chosen third party can connect. An approved route for one partner does not establish that another tool has the same rights.

Warehouse and report routes

Yardi’s warehouse products and MRI’s report outputs offer other extraction paths. They can support analytics without establishing write access, complete attachments or a migration-ready history. Keep those capabilities separate in a buying decision.

BEFORE YOU COMMIT

Ask for a route-specific answer

Request written terms and validate them against a representative tenant. The linked vendor profiles provide the evidence and the unresolved questions for each route.