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 Users API

User operations

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

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

This API exposes 3 operations across 3 paths, and defines 11 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.

3 operations 3 paths 11 schemas 3 GET

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 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Users 3

User operations

GET
/v1/users/{userUuid}
Get User
getUser 1 param → 200400401403404500
GET
/v1/users
List Users
listUsers 2 params → 200400401403404500
GET
/v1/buildings/{buildingUuid}/residents
List Building Residents
listBuildingResidents 3 params → 200400401403404500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are UserAccess (10 properties), User (6 properties), Resident (5 properties), UsersResponse (2 properties). Each schema is shown below with its type and property counts.

AccessGranter
object
Definition of the granter of Access
2 properties 2 required
UnauthorizedError
object
1 property 1 required
InternalServerError
object
1 property 1 required
ResidentsResponse
object
Response from the residents endpoint. Returns first 100 residents by default
2 properties 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
UsersResponse
object
Response from the users endpoint
2 properties 1 required
NotFoundError
object
1 property 1 required
Resident
object
Resident object
5 properties 4 required
BadRequestError
object
1 property 1 required
User
object
DOOR User object
6 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

door-users-api-openapi.yml Raw ↑

Other APIs Door publishes across the network.

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

This is an independent, third-party profile of Door Users 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.