OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured APIs across the declared product scope
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Export collections expose property, unit and lease records.
Rentvine manager API reference ↗
Export Leases / Export Properties / Export Units · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Export collections use page and pageSize parameters.
Rentvine manager API reference ↗
Export Leases / query parameters · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Export filters include modified-time bounds and object/status selectors.
Rentvine manager API reference ↗
Export Leases / dateTimeModifiedMin and Max · Checked 2026-10-16
Access cost barrier 10.0/10
Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligible
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Full API access included at no extra cost for vendors and customers.
Rentvine API eligibility and included cost ↗
Included at No Additional Cost · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Provider states developers can access without special team approval.
Rentvine API eligibility and included cost ↗
Public and Accessible / Direct Vendor Integrations · Checked 2026-10-16
Downstream permission -
-
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
The reviewed Rentvine route does not establish downstream permission.
Rentvine manager API reference ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update across business domains
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Tenant creation and bill create/update operations documented.
Rentvine manager API reference ↗
Create Tenant / Create Bill / Update Bill · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Vendors and developers can build autonomous custom integrations.
Rentvine open API integration boundary ↗
Open API / third-party solutions · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Export collections document modified-time bounds and triggering actions.
Rentvine manager API reference ↗
Export Leases / Last Modified Timestamp · Checked 2026-10-16
Limit visibility -
-
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
The reviewed Rentvine route does not establish limit visibility.
Rentvine manager API reference ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Modified timestamps identify updates; general deletion identities unestablished.
Rentvine manager API reference ↗
Export Leases / Last Modified Timestamp · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Re-enumerate current records to rebuild the disclosed scope; historical event replay, deletion recovery and full history are unverified.
Rentvine manager API reference ↗
Export Leases / Export Properties · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Authorized export endpoints return structured JSON outside the system.
Rentvine manager API reference ↗
Export Properties / Response · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Marketing promises 12 months; current §§1/3.d end access, so applicable retrieval rights remain unresolved.
Rentvine current service terms ↗
3.d Effect of Termination; compare provider data-ownership blog · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Portable scoped JSON records; complete files/history reconstruction unverified.
Rentvine manager API reference ↗
Export Leases / Response · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
Custom integrations can connect customer-chosen tools.
Rentvine open API integration boundary ↗
Open API · Checked 2026-10-16
Rights to custom logic -
-
Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate.
The reviewed Rentvine route does not establish rights to custom logic.
Rentvine manager API reference ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Customers create an API role, then generate an access key and secret in Settings. Rentvine states developers can integrate without special approval and supports independently built third-party connections.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Property, unit and lease export collections provide structured JSON with page/pageSize and modified-time bounds. Role grants limit what an integration can retrieve; inactive and voided records require explicit handling.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer role-scoped manager API | HTTP Basic | Customer | No | customer creates api role and access key/secret; api included; no separate developer approval advertised | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Provider guidance says the API is included at no additional cost for vendors and customers. Subscription quotes and onboarding charges are separate. A current numeric request-rate quota was not established.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The reference documents tenant creation and bill creation/update operations. Write permissions come from the key’s role; financial state and object validation remain operation-specific.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Export collections document which business changes advance modified timestamps. Updated-time polling does not establish a complete deletion stream or a retained replay checkpoint.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Modified timestamps identify updates; general deletion identities unestablished. | Rentvine manager API reference ↗Export Leases / Last Modified TimestampChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Re-enumerate current records to rebuild the disclosed scope; historical event replay, deletion recovery and full history are unverified. | Rentvine manager API reference ↗Export Leases / Export PropertiesChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Paginated JSON provides a scoped migration copy. A provider blog promises 12 months of post-cancellation access, while current service terms end access at termination; confirm the governing agreement before relying on that promise.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
External applications can implement customer rules. Native workflow artifact ownership and independent execution remain unresolved (customer data ownership does not establish native software ownership).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured APIs across the declared product scopeRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Export collections expose property, unit and lease records. | Rentvine manager API reference ↗Export Leases / Export Properties / Export UnitsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Export collections use page and pageSize parameters. | Rentvine manager API reference ↗Export Leases / query parametersChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Export filters include modified-time bounds and object/status selectors. | Rentvine manager API reference ↗Export Leases / dateTimeModifiedMin and MaxChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Provider states developers can access without special team approval. | Rentvine API eligibility and included cost ↗Public and Accessible / Direct Vendor IntegrationsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Full API access included at no extra cost for vendors and customers. | Rentvine API eligibility and included cost ↗Included at No Additional CostChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. The reviewed Rentvine route does not establish downstream permission. | Rentvine manager API reference ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update across business domainsRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Tenant creation and bill create/update operations documented. | Rentvine manager API reference ↗Create Tenant / Create Bill / Update BillChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Vendors and developers can build autonomous custom integrations. | Rentvine open API integration boundary ↗Open API / third-party solutionsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Export collections document modified-time bounds and triggering actions. | Rentvine manager API reference ↗Export Leases / Last Modified TimestampChecked 2026-10-16 |
| How are integration limits disclosed? | -Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. The reviewed Rentvine route does not establish limit visibility. | Rentvine manager API reference ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Authorized export endpoints return structured JSON outside the system. | Rentvine manager API reference ↗Export Properties / ResponseChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Marketing promises 12 months; current §§1/3.d end access, so applicable retrieval rights remain unresolved. | Rentvine current service terms ↗3.d Effect of Termination; compare provider data-ownership blogChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Custom integrations can connect customer-chosen tools. | Rentvine open API integration boundary ↗Open APIChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Rentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. The reviewed Rentvine route does not establish rights to custom logic. | Rentvine manager API reference ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedRentvine manager REST API 1.0 role-scoped customer Basic credentials, property/lease export collections and documented tenant/bill writes; native MCP is separate. Portable scoped JSON records; complete files/history reconstruction unverified. | Rentvine manager API reference ↗Export Leases / ResponseChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Resolution of marketing-versus-contract cancellation access conflict
- Numeric throughput and recovery guidance
- Complete deletion and retained replay semantics
- Complete files/history and native workflow portability
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.