Smart-lock API integration
Once the API is approved, issuing and revoking door codes joins the same operating layer as the books and the boards.
Door access is still a manual, per-property chore: issuing and revoking passcodes and keys by hand. I want programmatic control, issue and revoke, plus status and logs, wired into the same operating layer as everything else on this map.
How it works
It runs on the TTLock Cloud API. A developer app authenticates via OAuth2 (client id and secret, plus a hashed end-user credential, to a region token endpoint), then calls the lock APIs to issue and revoke passcodes and eKeys and read lock status and access logs. I verified the region routing by DNS, so a US account hits the global cloud base rather than the EU or China data centers, which would authenticate fine but return an empty lock list.
- OAuth2 against the correct regional endpoint, resolved and DNS-confirmed.
- Issue and revoke codes and eKeys, and read status and access logs.
- The credentials only appear after the developer app clears review.
It's building. The developer app is registered and in review, and the client id, secret, and webhook callback only unlock once it's approved. The auth flow and endpoints are already mapped and ready to wire in.
When it's live, access control joins the same agent layer as the books and the boards. One operating system, all the way down to the door.