Live lock state

The lock list and detail operations return cached connectivity. Connectivity tells you whether MyRemotely recently saw the lock online. It does not tell you whether the door is locked.

Use the live state operation when you need the current provider result:

curl --fail-with-body \
  --header "x-api-key: $MYREMOTELY_API_KEY" \
  'https://app.myremotely.ai/v1/locks/lock_demo_01/state'

A known state has a check time:

{
  "state": "unlocked",
  "checkedAt": "2026-09-16T12:00:03.000Z"
}

Provider and connectivity limits are normal outcomes. They return state: "unknown" with a stable reason and check time:

{
  "state": "unknown",
  "reason": "provider_timeout",
  "checkedAt": "2026-09-16T12:00:08.000Z"
}

Possible reasons are offline, unsupported_provider, provider_unavailable, provider_timeout, missing_lock_id, state_not_exposed, and provider_error.

This operation needs lock-state:read. It is read-only and does not call a vendor write operation. Responses use Cache-Control: no-store, so a successful live result is never replaced by an older cached value.