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 API for the declared product scope
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Lease lists return structured JSON records.
DoorLoop V1 list leases ↗
List all Leases /200 data · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Top-level list methods use page_size and page_number.
DoorLoop collection pagination ↗
Pagination · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Lease list parameters filter start/end dates and selected scope.
DoorLoop V1 list leases ↗
Query parameters / filter_start_date_from and filter_end_date_to · 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
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
The current entry One plan includes full API access; Connect and Multiply inherit it. Legacy Premium-only packaging has been replaced.
DoorLoop current One/Connect/Multiply pricing and API inclusion ↗
DoorLoop One: Includes / API access and Zapier / FAQ: What happened to Starter, Pro and Premium? · 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
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Current plans support connecting customer tools through the open API; the One plan includes API access.
DoorLoop current One/Connect/Multiply pricing and API inclusion ↗
DoorLoop One: Includes / API access and Zapier / FAQ: What happened to Starter, Pro and Premium? · Checked 2026-10-16
Downstream permission -
-
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
The reviewed DoorLoop route does not establish downstream permission.
DoorLoop V1 list leases ↗
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 in one business domain
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Lease creation and unit replacement update documented.
DoorLoop transactional lease creation ↗
Create a Lease / POST leases/full · Checked 2026-10-16
DoorLoop unit replacement update ↗
Update a Unit / replacement PUT semantics · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Customers connect custom applications using their account API keys.
DoorLoop current One/Connect/Multiply pricing and API inclusion ↗
API access / Integrate with any app · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism -
-
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
The reviewed DoorLoop route does not establish refresh mechanism.
DoorLoop V1 list leases ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Credential/IP numeric limits, headers and 429/403 recovery guidance published.
DoorLoop credential and IP rate limits ↗
Per credential / Per source IP / Reaching a limit · Checked 2026-10-16
CDC and deletion capture -
-
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
The reviewed DoorLoop route does not establish cdc and deletion capture.
DoorLoop V1 list leases ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Re-enumerate current records to rebuild the disclosed scope; historical event replay, deletion recovery and full history are unverified.
DoorLoop V1 list leases ↗
List all Leases · 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
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Lease JSON responses can leave through customer-authorized keys.
DoorLoop V1 list leases ↗
200 response / data · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
The reviewed DoorLoop route does not establish post-cancellation access.
DoorLoop V1 list leases ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Portable lease records; whole-account attachments/history unverified.
DoorLoop V1 list leases ↗
List all Leases · 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
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
Current One-plan open API supports customer-chosen integrations.
DoorLoop current One/Connect/Multiply pricing and API inclusion ↗
DoorLoop One: Includes / API access and Zapier / FAQ: What happened to Starter, Pro and Premium? · Checked 2026-10-16
Rights to custom logic -
-
DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate.
The reviewed DoorLoop route does not establish rights to custom logic.
DoorLoop V1 list leases ↗
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 manage keys in Zapier & API Keys. Each token has an access role, and endpoint permissions follow the token and underlying user; V2 OAuth has a separate authentication contract.
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
Lease collections return JSON data and totals. Pagination defaults to 50 and caps at 1,000 records per page; lease-tenant correlation has a separate endpoint.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| One-plan V1 customer bearer key | API key | Customer | No | current one plan includes api access; customer key access role and underlying user permissions | 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
DoorLoop One includes full API access; Connect and Multiply inherit it. Current pricing replaces the legacy Starter/Pro/Premium tiers. The limit guide states 50 requests/minute and 500/hour per credential, with rolling windows, plus 10 requests/second sustained per egress IP.
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
POST /leases/full creates a lease transaction with charges and tenant move-in. Unit PUT is replacement-style, so omitted writable fields can be lost; obtain the current record before editing.
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 reviewed V1 route establishes repeated collection reads, but no general modified-since cursor, deletion feed or retained event replay. Collection pagination is not a change checkpoint.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. The reviewed DoorLoop route does not establish cdc and deletion capture. | DoorLoop V1 list leases ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Re-enumerate current records to rebuild the disclosed scope; historical event replay, deletion recovery and full history are unverified. | DoorLoop V1 list leases ↗List all LeasesChecked 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 lease JSON supports a customer-held record copy. Complete documents, historical accounting and independent restore remain unverified (an audit-log feature does not establish an exportable change log).
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
Customer applications can implement external rules through the documented API. Native workflow artifact rights and post-cancellation retrieval remain unresolved.
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 API for the declared product scopeDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Lease lists return structured JSON records. | DoorLoop V1 list leases ↗List all Leases /200 dataChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Top-level list methods use page_size and page_number. | DoorLoop collection pagination ↗PaginationChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Lease list parameters filter start/end dates and selected scope. | DoorLoop V1 list leases ↗Query parameters / filter_start_date_from and filter_end_date_toChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Current plans support connecting customer tools through the open API; the One plan includes API access. | DoorLoop current One/Connect/Multiply pricing and API inclusion ↗DoorLoop One: Includes / API access and Zapier / FAQ: What happened to Starter, Pro and Premium?Checked 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 eligibleDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. The current entry One plan includes full API access; Connect and Multiply inherit it. Legacy Premium-only packaging has been replaced. | DoorLoop current One/Connect/Multiply pricing and API inclusion ↗DoorLoop One: Includes / API access and Zapier / FAQ: What happened to Starter, Pro and Premium?Checked 2026-10-16 |
| What permission is needed for the documented downstream use? | -DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. The reviewed DoorLoop route does not establish downstream permission. | DoorLoop V1 list leases ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Lease creation and unit replacement update documented. | DoorLoop transactional lease creation ↗Create a Lease / POST leases/fullChecked 2026-10-16 DoorLoop unit replacement update ↗Update a Unit / replacement PUT semanticsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Customers connect custom applications using their account API keys. | DoorLoop current One/Connect/Multiply pricing and API inclusion ↗API access / Integrate with any appChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | -DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. The reviewed DoorLoop route does not establish refresh mechanism. | DoorLoop V1 list leases ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Credential/IP numeric limits, headers and 429/403 recovery guidance published. | DoorLoop credential and IP rate limits ↗Per credential / Per source IP / Reaching a limitChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Lease JSON responses can leave through customer-authorized keys. | DoorLoop V1 list leases ↗200 response / dataChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. The reviewed DoorLoop route does not establish post-cancellation access. | DoorLoop V1 list leases ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Current One-plan open API supports customer-chosen integrations. | DoorLoop current One/Connect/Multiply pricing and API inclusion ↗DoorLoop One: Includes / API access and Zapier / FAQ: What happened to Starter, Pro and Premium?Checked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -DoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. The reviewed DoorLoop route does not establish rights to custom logic. | DoorLoop V1 list leases ↗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 unverifiedDoorLoop V1 REST API with customer role-scoped bearer keys, lease list/create and unit update operations; V2 OAuth and Zapier product behavior are separate. Portable lease records; whole-account attachments/history unverified. | DoorLoop V1 list leases ↗List all LeasesChecked 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
- V1 change/deletion feed and replay retention
- Whole-account files/history migration
- Native workflow rights and cancellation retrieval
- V2 OAuth production/distribution requirements
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.