Set or change the app-lock PIN

Requires currentPin when a lock already exists. A wrong currentPin counts against the same attempt budget as the lock screen — otherwise an unlocked session could guess the PIN without limit and learn it for every future lock.

post/auth/app-lock

Request body

pinstring required

The new PIN, 4-6 digits. Its length is what the client renders from later; a separate length field is not accepted, because two values that can disagree is a bug rather than a convenience.

currentPinstring

Required when a lock already exists. Changing a PIN proves knowledge of the current one, and a wrong value counts against the same attempt budget as the lock screen — otherwise an unlocked session is an unlimited PIN oracle.

Example request

{
  "pin": "1234",
  "currentPin": "1234"
}

Response

PIN set

Changes

No recorded changes to this endpoint across all 1 revision of this API.