Door website screenshot

Door

DOOR (formerly Latch) is a multifamily proptech company providing a smart-building access and building-intelligence platform. It unifies smart locks, readers, intercoms, cameras, thermostats and sensors with software (DOOR OS) for property managers, and integrates with property-management systems such as Yardi, RealPage, Entrata, and AppFolio. DOOR exposes its capabilities to authorized partners through OpenDOOR - a set of REST APIs plus native iOS, Android, and Web SDKs - letting partner apps enumerate buildings, doors, keys, and users and grant, update, or revoke resident access. The API is secured with Auth0-issued JWTs (partner-scoped machine-to-machine and user-scoped passwordless tokens). This profile was enriched by the API Evangelist pipeline from DOOR's public developer hub at developers.door.com.

Door publishes 6 APIs on the APIs.io network, including Access Management API, Buildings API, Doors and Keys API, and 3 more. Tagged areas include Company, Access Control, Smart Building, PropTech, and Physical Security.

Door’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, authentication, and 24 more developer resources.

40.5/100 developing ▬ flat Agent 37/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessSelf serve
2 APIs
CompanyAccess ControlSmart BuildingPropTechPhysical SecurityIoTMultifamilyReal-EstateSmart LockBuilding Automation

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/door: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Door Access Management API

User access management operations

Door Buildings API

Building operations

Door Doors and Keys API

Door/Key and key operations

Door Partner Authentication API

Partner authentication operations

Door User Authentication API

User authentication operations

Door Users API

User operations

Open Collections 7

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Scroll for all 7

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Door Authentication

http/oauth2 · 3 schemes

SECURITY

Door Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Door Agentic Access

15 operations · 8 acting · 1 human-in-the-loop

15 operations · 8 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: door
name: Door
description: DOOR (formerly Latch) is a multifamily proptech company providing a smart-building access and building-intelligence
  platform. It unifies smart locks, readers, intercoms, cameras, thermostats and sensors with software (DOOR OS) for property
  managers, and integrates with property-management systems such as Yardi, RealPage, Entrata, and AppFolio. DOOR exposes its
  capabilities to authorized partners through OpenDOOR - a set of REST APIs plus native iOS, Android, and Web SDKs - letting
  partner apps enumerate buildings, doors, keys, and users and grant, update, or revoke resident access. The API is secured
  with Auth0-issued JWTs (partner-scoped machine-to-machine and user-scoped passwordless tokens). This profile was enriched
  by the API Evangelist pipeline from DOOR's public developer hub at developers.door.com.
url: https://raw.githubusercontent.com/api-evangelist/door/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://cdn.prod.website-files.com/6838ad705264e74df1653563/683f3efb468620cdf85dd643_door-logo-webclip.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- techstars
x-tier: enriched
x-tier-reason: developer-hub-openapi
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- Company
- Access Control
- Smart Building
- PropTech
- Physical Security
- IoT
- Multifamily
- Real-Estate
- Smart Lock
- Building Automation
tags_raw:
- Company
- Access Control
- Smart Building
- Proptech
- Physical Security
- IoT
- Multifamily
- Real Estate
- Smart Lock
- Building Automation
apis:
- aid: door:door-access-management-api
  name: Door Access Management API
  description: User access management operations
  humanURL: https://developers.door.com/reference
  baseURL: https://rest.latchaccess.com/access/sdk
  tags:
  - Access Management
  properties:
  - type: OpenAPI
    url: openapi/door-access-management-api-openapi.yml
- aid: door:door-buildings-api
  name: Door Buildings API
  description: Building operations
  humanURL: https://developers.door.com/reference
  baseURL: https://rest.latchaccess.com/access/sdk
  tags:
  - Buildings
  properties:
  - type: OpenAPI
    url: openapi/door-buildings-api-openapi.yml
- aid: door:door-doors-and-keys-api
  name: Door Doors and Keys API
  description: Door/Key and key operations
  humanURL: https://developers.door.com/reference
  baseURL: https://rest.latchaccess.com/access/sdk
  tags:
  - Doors and Keys
  properties:
  - type: OpenAPI
    url: openapi/door-doors-and-keys-api-openapi.yml
- aid: door:door-partner-authentication-api
  name: Door Partner Authentication API
  description: Partner authentication operations
  humanURL: https://developers.door.com/reference
  baseURL: https://rest.latchaccess.com/access/sdk
  tags:
  - Partner Authentication
  properties:
  - type: OpenAPI
    url: openapi/door-partner-authentication-api-openapi.yml
- aid: door:door-user-authentication-api
  name: Door User Authentication API
  description: User authentication operations
  humanURL: https://developers.door.com/reference
  baseURL: https://rest.latchaccess.com/access/sdk
  tags:
  - User Authentication
  properties:
  - type: OpenAPI
    url: openapi/door-user-authentication-api-openapi.yml
- aid: door:door-users-api
  name: Door Users API
  description: User operations
  humanURL: https://developers.door.com/reference
  baseURL: https://rest.latchaccess.com/access/sdk
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/door-users-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://door.com/
- type: DeveloperPortal
  url: https://developers.door.com/
- type: Documentation
  url: https://developers.door.com/docs
- type: APIReference
  url: https://developers.door.com/reference
- type: GettingStarted
  url: https://developers.door.com/docs
- type: Support
  url: https://support.door.com/hc/en-us
- type: Blog
  url: https://door.com/articles
- type: SignUp
  url: https://app.door.com
- type: Login
  url: https://app.door.com
- type: TermsOfService
  url: https://door.com/policy/terms-of-service
- type: PrivacyPolicy
  url: https://door.com/policy/privacy
- type: StatusPage
  url: https://status.latch.com
- type: Deprecation
  url: https://developers.door.com/docs/migrating-from-latch-sdk-v1-to-opendoor-sdk-v2.md
- type: Authentication
  url: authentication/door-authentication.yml
- type: Conventions
  url: conventions/door-conventions.yml
- type: ErrorCatalog
  url: errors/door-problem-types.yml
- type: ErrorCatalog
  name: Error code registry
  url: errors/door-error-codes.yml
- type: Lifecycle
  url: lifecycle/door-lifecycle.yml
- type: Conformance
  url: conformance/door-conformance.yml
- type: DataModel
  url: data-model/door-data-model.yml
- type: Packages
  url: packages/door-packages.yml
- type: SDKs
  url: packages/door-packages.yml
- type: X-MCPServerCandidate
  url: mcp/door-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/door-llms.txt
- type: WellKnown
  url: well-known/door-well-known.yml
- type: Overlay
  url: overlays/door-partner-overlay.yaml
- type: DomainSecurity
  url: security/door-domain-security.yml
- type: AgenticAccess
  url: agentic-access/door-agentic-access.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Sandbox
  url: sandbox/door-sandbox.yml
- type: ChangeLog
  url: changelog/door-changelog.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/door"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/door/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/door/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.