OVERALL CONTROL / 0.4-documentary
Grades and scoring
Overall C / 5.2*/10, based on 13 of 14 documented answers (export completeness and reliability require live tests).
Core with a contracted API-partner route, Data Share / Data Direct and separately subscribed Pro Agent Builder. Agent ownership and data-product restrictions remain separate.
Each dimension contributes one sixth of the overall grade. Data access is capped by the commercial barrier on the assessed read routes. Open the inputs below to see the enum answer, route, scoring anchor and source clause.
Data access
Scored answers and evidence
Read interface 7.5/10
Structured APIs across business domains
Entrata / contracted API route
Typed leasing, accounting, customer and maintenance interfaces are documented.
Entrata public OpenAPI specification ↗
OpenAPI paths and component schemas · Checked 2026-10-09
Bulk delivery 10.0/10
Recurring feed to a customer-selected data environment
Entrata Core / Data Share
Customer-selected BI and warehouse destinations are supported; this does not guarantee all records or attachments.
US product-specific terms: Core, data products and Pro ↗
Business Intelligence / Data Share: introduction and 2.4 · Checked 2026-10-09
Query expressiveness 5.0/10
Documented structured API filters
Entrata / contracted API services
Service filters are documented; pagination is not established by the reviewed lease and work-order request schemas. Data Direct and Data Share legal terms alone do not establish an external SQL query interface.
Entrata public OpenAPI specification ↗
getWorkOrders and getLeases request filters · Checked 2026-10-09
Access cost barrier 2.5/10
Access requires an individually negotiated project or agreement
Entrata Core / Data Share
Consulting or implementation charges and contracted property rates apply. Exact pricing requires a quote.
US product-specific terms: Core, data products and Pro ↗
Business Intelligence / Data Share: introduction and 1.1 · Checked 2026-10-09
Third-party accessibility
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Entrata / API partner
A contracted partner route has provider review and security obligations.
API Partner Security Requirements & Obligations ↗
API Partner Security Requirements and Obligations · Checked 2026-10-09
Downstream permission 5.0/10
Separate consent for the third party or declared use
API partner / Entrata-derived data and external AI
External AI processing requires written approval on this route. Separately, Data Direct 2.5 restricts model use with provider-confidential schema and equivalent-platform replication; not a blanket ban on all customer data.
API Partner Security Requirements & Obligations ↗
Sections 2 and 4.8: external AI processing · Checked 2026-10-09
US product-specific terms: Core, data products and Pro ↗
Data Direct 2.4–2.5: confidentiality and restrictions · Checked 2026-10-09
External action
Scored answers and evidence
Write interface 7.5/10
Create and update across business domains
Entrata / permitted API services
Creation and updates span financial and operational services; grants and service limits still apply.
Entrata public OpenAPI specification ↗
sendJournalEntries; sendLeads; updateLease; sendWorkOrders · Checked 2026-10-09
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Entrata / approved API partner application
The reviewed partner path does not establish unrestricted self-service custom applications.
API documentation access notice ↗
Documentation access requirements · Checked 2026-10-09
Continuity
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Entrata API / selected services
Date filters support incremental queries for named services; no complete change/deletion stream is inferred.
Entrata public OpenAPI specification ↗
getWorkOrders: lastUpdatedOnFromDate; getVendorLocations: lastModifiedOn · Checked 2026-10-09
Limit visibility 7.5/10
Service-specific limits disclosed in runtime headers
Entrata API / per-service limits
Per-minute, hourly and daily limits are disclosed in service response headers. Numeric allowances were not measured.
Entrata public OpenAPI specification ↗
info.description: Throttling · Checked 2026-10-09
Data exit
Scored answers and evidence
Export custody 10.0/10
Feed into a customer-controlled store
Entrata Core / Data Direct and Data Share
Customers manage external connections and custody after delivery. Export custody does not remove downstream-use restrictions.
US product-specific terms: Core, data products and Pro ↗
Data Direct 2.1; Data Share 2.4 · Checked 2026-10-09
Cancellation access -
-
Entrata Core / customer agreement
These product terms do not establish the master agreement’s cancellation retrieval window or exit charge.
US product-specific terms: Core, data products and Pro ↗
Core, Data Direct and Data Share terms · Checked 2026-10-09
Business logic and customization
Scored answers and evidence
Logic authoring 5.0/10
Customer-editable native workflows or agent configurations
Entrata Pro / Agent Builder (separate subscription)
Customers create, configure, test, version and publish native agents. Subscription is separate; independent runtime execution is not established.
US product-specific terms: Core, data products and Pro ↗
Entrata Pro 1.2 and 4.1–4.2 (updated 07 Oct 2026) · Checked 2026-10-09
Rights to custom logic 0.0/10
Provider owns custom workflow artifacts with assignment of remaining rights
Entrata Pro / Agent Builder artifacts
Provider owns created agents with assignment of remaining rights. Customer input and generated output have separate ownership clauses (3.2–3.3).
US product-specific terms: Core, data products and Pro ↗
Entrata Pro 4.4: Ownership of Agents · Checked 2026-10-09
* Scores with unresolved inputs show the midpoint of their possible scores (document-based assessment). Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
The public partner and API materials describe an agreement-based integration path. Customer permission controls do not establish a universal exemption from provider approval.
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
The available routes include approved partner API access from conditional customer report delivery. Required methods, properties, fields and report formats need confirmation for the selected route.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Entrata approved API partner with customer-scoped key | API key | Customer | Yes | Contract required | 2026-09-21 |
| Entrata customer report exports (conditional) | No separate connector credentials | Customer | Not confirmed | Not confirmed | 2026-09-21 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
No complete numeric API fee schedule or dependable end-to-end approval SLA was confirmed in the linked sources. Obtain a current agreement, scope and quote before estimating access cost.
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 current public specification includes financial and operational writes, including journal entries, leads, leases and work orders. Grants, retry safety and successful execution still need verification.
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
The current contract needs to establish paging, changed-since filters, deletion signals and webhook recovery. Treat notifications as hints until replay and ordering are documented.
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost property permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Entrata advertises configurable reporting and exports. The exact machine-readable output, completeness and permission for downstream processing remain route-specific checks.
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
Entrata retains ownership, including custom-request agents; remaining customer rights are assigned to Entrata.
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 checked 09 Oct 2026. Every answer has its own scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Published maximum time from a complete request to usable access? | -Entrata / new API partner The reviewed process does not establish a maximum elapsed time to the first usable customer query. Required review or pilot steps do not establish a duration. | API Partner Security Requirements & Obligations ↗Pre-production review and approvallegal terms · checked 2026-10-09 |
| Mandatory one-time customer access setup fee? | -Entrata Core / Data Share customer Consulting hours and/or implementation fees are mandatory; the amount is in the customer order and is not published here. | US product-specific terms: Core, data products and Pro ↗Business Intelligence / Data Share introductionlegal terms · checked 2026-10-09 |
| Is an API access route advertised? | YesEntrata / contracted API route API use requires an agreement with the integrating company. | API documentation access notice ↗Important Noticeprogram requirements · checked 2026-10-09 |
| Does the partner route require provider approval? | YesEntrata / contracted API-partner route Pre-approval applies before credentials or production access. | API Partner Security Requirements & Obligations ↗§1; §3legal terms · checked 2026-10-09 |
| Does the integrating company need a provider agreement? | YesEntrata / contracted API-partner route The notice expressly requires a company agreement. | API documentation access notice ↗Important Noticeprogram requirements · checked 2026-10-09 |
| What permission is required for external AI processing? | Written approvalAPI partners / Entrata-derived data Includes inference, classification and training; narrow approved use can receive different risk treatment. | API Partner Security Requirements & Obligations ↗§2: AI/ML Use; §4.8legal terms · checked 2026-10-09 |
| What permission is required for onward data sharing? | Written approvalAPI partners / Entrata-derived data Onward sharing and secondary use need express written authorization. | API Partner Security Requirements & Obligations ↗§4.1legal terms · checked 2026-10-09 |
| When is independent security attestation required? | Risk-based requirementAPI partner security tiers Tier 3 requires SOC 2 Type II or an accepted equivalent; lower tiers are conditional. | API Partner Security Requirements & Obligations ↗§5.1–5.4legal terms · checked 2026-10-09 |
| What write capability is documented? | Specific write operationsEntrata / permitted API services Financial and operational write methods are documented; grants, retry safety and actual results need testing. | Entrata public OpenAPI specification ↗sendJournalEntries; sendLeads; updateLease; sendWorkOrdersproduct documentation · checked 2026-10-09 |
| What change mechanism is documented? | Updated-since filtersEntrata / selected API services Incremental date filters are available for named services; full deletion capture and replay remain unverified. | Entrata public OpenAPI specification ↗getWorkOrders and getVendorLocations date filtersproduct documentation · checked 2026-10-09 |
| What export output is documented? | Reports; formats unspecifiedEntrata Reporting Scheduled downloads are advertised; the reviewed page does not name formats. | Reporting ↗Distribution toolsproduct documentation · checked 2026-10-09 |
| Must the partner return or delete data at termination? | YesAPI partner / Common Client data Return or delete at client termination, agreement termination or written request; backups follow a documented lifecycle. | API Partner Security Requirements & Obligations ↗§4.6legal terms · checked 2026-10-09 |
| Is a complete records, history and attachments export established? | -Entrata Reporting The overview provides no complete records, history and attachments manifest. | Reporting ↗Distribution toolsproduct documentation · checked 2026-10-09 |
| Who owns custom workflows under the reviewed terms? | Provider owns workflowsUS Core / custom Workflow Agents Entrata retains ownership, including custom-request agents; remaining customer rights are assigned to Entrata. | US product-specific terms: Core, data products and Pro ↗Core §1.3: Ownership of Agents (updated 16 Apr 2026)legal terms · checked 2026-10-09 |
| Can customers export workflow definitions for use elsewhere? | -US Core / Workflow Agents These clauses do not grant portable workflow-definition export. | US product-specific terms: Core, data products and Pro ↗Core §1.2–1.3legal terms · checked 2026-10-09 |
14 questions still to research
- Published development/review estimate: lower end?
- Published development/review estimate: upper end?
- Measured time from a complete request to the first usable query?
- Annual partner interface license amount?
- Can data replicate to a customer warehouse?
- Is a security questionnaire required?
- Minimum company history for the partner program?
- Minimum existing clients for the partner program?
- Is an annual interface license fee required?
- Published customer integration add-on price?
- Published minimum customer integration add-on spend?
- Notice for termination without cause?
- Does API access continue after agreement termination?
- Is a customer custom-API toolkit documented?
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
- Current licensed method and field coverage
- Numeric API fees and approval time
- Report formats and complete exit coverage
Documentation
Published 09 Oct 2026. This is the first profile version. Source dates differ; the overview-page recheck does not replace each source’s original verification date.