How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Door Access Management API

User access management operations

Door Access Management API is one of 6 APIs that Door publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Access Management. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 4 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://auth.prod.latch.com.

5 operations 4 paths 17 schemas 1 DELETE1 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://rest.latchaccess.com/access/sdk
License
Terms of Service
Resource Areas
1

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 1 DELETE, 1 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Access Management 5

User access management operations

POST
/v1/users
Grant Access to User
grantAccessToUser body → 200201400401403404500
POST
/v2/users
Grant Access to User V2
grantAccessToUserV2 body → 200201400401403404500
GET
/v1/keys/{keyUuid}/accesses
List Accesses By Key
listKeyAccesses 1 param → 200400401403404500
DELETE
/v1/users/{userUuid}/doors/{doorUuid}
Revoke User Access
revokeUserAccess 2 params → 200204401403404500
PATCH
/v1/users/{userUuid}/doors/{doorUuid}
Update User Access
updateUserAccess 2 params body → 200204400401403404500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are PostUserRequest (12 properties), UserAccess (10 properties), KeyAccess (9 properties), Door (8 properties). Each schema is shown below with its type and property counts.

PostUserResponse
object
Response from the post users endpoint
2 properties 2 required
AccessGranter
object
Definition of the granter of Access
2 properties 2 required
Battery
object
Information on the device battery.
2 properties 2 required
KeyAccessesResponse
object
Response from the key accesses endpoint
1 property 1 required
InternalServerError
object
1 property 1 required
UnauthorizedError
object
1 property 1 required
Doorcode
object
Doorcode object
2 properties 2 required
UserAccess
object
Definition of a User's Access to a Door/Key and the metadata associated
10 properties 6 required
Door
object
DOOR Door/Key object
8 properties 4 required
NotFoundError
object
1 property 1 required
KeyAccess
object
A user's access to a key, with per-door/key data grouped in the doors/keys list
9 properties 7 required
KeyAccessDoor
object
Door/Key-specific data within a key access
2 properties 1 required
PostUserRequest
object
JSON representation of the user for the post users endpoint
12 properties 5 required
BadRequestError
object
1 property 1 required
UpdateUserDoorRequest
object
JSON representation of the user's access to the door/key to update for the patch users door/key endpoint
3 properties
User
object
DOOR User object
6 properties 4 required
DeviceInfo
object
Additional information about the physical lock device.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

door-access-management-api-openapi.yml Raw ↑

Other APIs Door publishes across the network.

Door Buildings API
Door Doors and Keys API
Door Partner Authentication API
Door User Authentication API
Door Users API
Where this information came from

This is an independent, third-party profile of Door Access Management API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.