Skip to main content

Overview

Completes the device pairing flow by claiming an entry key (the 7-character code displayed on the thermostat) and associating the device with a user. After a successful registration:
  1. The entry key is marked as claimed
  2. An ownership record is created linking the device to the user
  3. The user bucket and structure bucket are pushed to the device, completing the pairing dialog on-screen

Endpoint

Request

The code field is case-insensitive and automatically uppercased.

Response

Success (200 OK)

Failure — Invalid/Expired/Already Claimed (200 OK)

Registration failures return 200 OK (not 4xx) to match the protocol convention. Check the success field.

Error (400 Bad Request)

Pairing Completion

After registration, the server pushes two buckets to the device through any held subscribe connection:
  1. user.{userId} bucket with {"name": "{userId}"} — this is what triggers the pairing screen to dismiss on the device
  2. structure.{structureId} bucket with {"name": "Home", "devices": [serial]} — establishes the home association
If the device has no active subscribe connection at registration time, the buckets are stored and will be sent on the next subscribe.

Examples

GET /nest/passphrase

Entry key generation on the device

GET /api/devices

List registered devices