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 API contracts indexed 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 Buildings, PropTech, and Physical Security.

The Door catalog on APIs.io includes 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

45.5/100 developing ▬ flat Agent 38/100 agent ready Front door AI 1/6 silent Heartbeat 94/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 2 Agent Skills

Company Access Control Smart Buildings PropTech Physical Security IoT Multifamily Real Estate Smart Lock Building Automation

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 45.5/100 · developing

Contract Quality 9.0 / 19

Developer Ergonomics 10.4 / 15

Access Clarity 3.2 / 15

Operational Transparency 3.9 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 38/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/door/"><img src="https://apis.io/badge/door/card.svg" alt="Door on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 21.1 — up to +15.8 composite points
Contract Quality scores 47.9 — up to +13.0 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/door/apis.yml: open an issue on github.com/api-evangelist/door to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
ONVIF Video Analytics (video surveillance, edge cameras, computer vision)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

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 6

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

Authentication Access Management API

OPEN COLLECTION

Authentication Access Management Buildings API

OPEN COLLECTION

Authentication Access Management Doors and Keys API

OPEN COLLECTION

Authentication Access Management Partner Authentication API

OPEN COLLECTION

Authentication Access Management User Authentication API

OPEN COLLECTION

Authentication Access Management Users API

OPEN COLLECTION

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Audit and revoke resident access

AGENT SKILL

Grant a resident access to doors

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Door API Rules

69 rules · 67 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 2

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Door Authentication Overlay

1 action · update · door-authentication-openapi.json

DERIVED

Door Partner Overlay

2 actions · update · door-partner-openapi.json

DERIVED

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

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

LLMsTxt

WellKnown

AgenticAccess

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

Support

StatusPage

Deprecation

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

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: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  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'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-25
tags:
- Company
- Access Control
- Smart Buildings
- 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
- Real-Estate
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:
  - Identity and Access Management
  tags_raw:
  - 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

Door API — frequently asked questions

Does Door have an API?

Yes. APIs.io lists 6 APIs from Door, including Door Access Management API, Door Buildings API and Door Doors and Keys API, and 3 more.

Is there an OpenAPI specification for the Door API?

Yes. APIs.io indexes 6 OpenAPI specifications for Door, each linked for download from this page.

How do I authenticate with the Door API?

Door documents its authentication (http/oauth2 · 3 schemes). The details are profiled on APIs.io as Door Authentication.

Is the Door API ready for AI agents?

Door has a Kin Score of 45.5 out of 100 (developing) and an Agent Readiness score of 37.9 (agent-ready), scored by API Evangelist on 2026-11-06.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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