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
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
Partner methods cover units, residents and work orders.
ResMan API access by partner category ↗
API Access / Call Center and Collections · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
ResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification.
GetUnits returns the unit collection for each granted property.
ResMan Property API reference ↗
GetUnits · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
ResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification.
Event requests accept StartDate/EndDate and property scope.
ResMan Events API reference ↗
GetCompletedWorkOrders / GetMoveIns · Checked 2026-10-16
Access cost barrier -
-
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
Current fees and minimum package remain unresolved.
ResMan API introduction linked from provider portal ↗
Reviewed documentation; no applicable scoring contract established · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
Integration Partner approval precedes any API access.
ResMan Partner API v2 provider Postman documentation ↗
Getting started guide · Checked 2026-10-16
Downstream permission -
-
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
Applicable downstream processing terms remain unresolved.
ResMan API introduction linked from provider portal ↗
Reviewed documentation; no applicable scoring contract 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
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
V2 maps work-order POST/PATCH and market-rent writes.
ResMan Partner API v2 provider Postman documentation ↗
Converting from Version 1 / WorkOrders and MarketRent · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
Partner applications use approved credentials and client account headers.
ResMan Partner API v2 provider Postman documentation ↗
Getting started guide / Authentication · 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
ResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification.
Business-event date windows support scoped repeat extraction.
ResMan Events API reference ↗
GetCompletedWorkOrders / GetMoveOuts · Checked 2026-10-16
Limit visibility -
-
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
Numeric quotas and throttle recovery remain unresolved.
ResMan API introduction linked from provider portal ↗
Reviewed documentation; no applicable scoring contract established · Checked 2026-10-16
CDC and deletion capture -
-
ResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification.
Business events do not establish a generic update/deletion contract.
ResMan Events API reference ↗
Reviewed documentation; no applicable scoring contract established · Checked 2026-10-16
Replay and gap recovery -
-
ResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification.
Date queries do not establish retention or durable consumer checkpoints.
ResMan Events API reference ↗
Reviewed documentation; no applicable scoring contract established · 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
ResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification.
JSON or XML unit collections are returned externally.
ResMan Property API reference ↗
GetUnits / Response · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
No applicable cancellation retrieval clause established.
ResMan API introduction linked from provider portal ↗
Reviewed documentation; no applicable scoring contract established · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
ResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification.
Resident responses include structured identities and optional lease history; whole-product coverage unverified.
ResMan Leasing API reference ↗
GetApplicantsAndCurrentResidents · 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
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
Applications invoke methods over HTTPS POST.
ResMan API introduction linked from provider portal ↗
General / Request Example · Checked 2026-10-16
Rights to custom logic -
-
ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference.
Native workflow artifact ownership and reuse unresolved.
ResMan API introduction linked from provider portal ↗
Reviewed documentation; no applicable scoring contract 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
Integration Partner approval is required. V2 sends partner ID and API key through Basic authentication and ResMan-Account-Id in a header; legacy v1 uses request parameters.
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
V2 maps units, work orders and accounting reads to resource routes. Legacy v1 separately documents property-unit collections, optional resident lease history and date-window business events.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Partner API v2 | HTTP Basic | Integration provider | Yes | integration partner approval; basic partner id/api key; resman-account-id header | 2026-10-16 |
| Legacy partner API v1 | API key | Integration provider | Yes | legacy v1 partner credentials and account/property parameters; confirm availability and v2 migration | 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
The reviewed partner reference does not establish current access fees, minimum customer package or a numeric request quota. Confirm the commercial agreement before implementation.
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
Partner categories list lead, work-order and resident-transaction writes. Availability depends on the methods granted to that partner.
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
Date-window event queries cover move-ins, move-outs and completed work orders. Those business events do not establish a generic record-deletion feed or durable consumer checkpoint.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -ResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification. Business events do not establish a generic update/deletion contract. | ResMan Events API reference ↗Reviewed documentation; no applicable scoring contract establishedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | -ResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification. Date queries do not establish retention or durable consumer checkpoints. | ResMan Events API reference ↗Reviewed documentation; no applicable scoring contract establishedChecked 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
JSON/XML collection responses support a customer-held copy of the granted records. Attachments, historical completeness and termination retrieval rights remain unresolved.
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 integration code can act on returned records. Native workflow definitions and reuse rights need separate evidence (a move-out is not proof that a person record was deleted).
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 scopeResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. Partner methods cover units, residents and work orders. | ResMan API access by partner category ↗API Access / Call Center and CollectionsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification. GetUnits returns the unit collection for each granted property. | ResMan Property API reference ↗GetUnitsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification. Event requests accept StartDate/EndDate and property scope. | ResMan Events API reference ↗GetCompletedWorkOrders / GetMoveInsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. Integration Partner approval precedes any API access. | ResMan Partner API v2 provider Postman documentation ↗Getting started guideChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. Current fees and minimum package remain unresolved. | ResMan API introduction linked from provider portal ↗Reviewed documentation; no applicable scoring contract establishedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. Applicable downstream processing terms remain unresolved. | ResMan API introduction linked from provider portal ↗Reviewed documentation; no applicable scoring contract establishedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update across business domainsResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. V2 maps work-order POST/PATCH and market-rent writes. | ResMan Partner API v2 provider Postman documentation ↗Converting from Version 1 / WorkOrders and MarketRentChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. Partner applications use approved credentials and client account headers. | ResMan Partner API v2 provider Postman documentation ↗Getting started guide / AuthenticationChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification. Business-event date windows support scoped repeat extraction. | ResMan Events API reference ↗GetCompletedWorkOrders / GetMoveOutsChecked 2026-10-16 |
| How are integration limits disclosed? | -ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. Numeric quotas and throttle recovery remain unresolved. | ResMan API introduction linked from provider portal ↗Reviewed documentation; no applicable scoring contract establishedChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification. JSON or XML unit collections are returned externally. | ResMan Property API reference ↗GetUnits / ResponseChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. No applicable cancellation retrieval clause established. | ResMan API introduction linked from provider portal ↗Reviewed documentation; no applicable scoring contract establishedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. Applications invoke methods over HTTPS POST. | ResMan API introduction linked from provider portal ↗General / Request ExampleChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -ResMan Partner API v2 with Basic partner authentication and account header; separately scoped legacy v1 collection/event methods retained in the provider reference. Native workflow artifact ownership and reuse unresolved. | ResMan API introduction linked from provider portal ↗Reviewed documentation; no applicable scoring contract establishedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedResMan legacy v1 published property, leasing and business-event methods; v2 compatibility and endpoint-level semantics require verification. Resident responses include structured identities and optional lease history; whole-product coverage unverified. | ResMan Leasing API reference ↗GetApplicantsAndCurrentResidentsChecked 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
- Partner fees, rate limits and onboarding time
- Granted methods per partner category
- General change/deletion capture and replay retention
- Attachment completeness and cancellation rights
- Native workflow ownership and portability
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.