dev.cocore.devicePair.confirm
{
"$type": "com.atproto.lexicon.schema",
"defs": {
"main": {
"description": "Approve or deny a pending device-pairing attempt, identified by the `userCode` the device displayed. Called from the verification UI by a signed-in user. Approving requires the provider `session` to grant to the device.",
"errors": [
{
"description": "Missing `userCode`, an invalid `decision`, or `approve` without a `session`.",
"name": "InvalidRequest"
},
{
"description": "No pairing attempt matches the `userCode`.",
"name": "NotFound"
},
{
"description": "The pairing attempt could not be approved in its current state.",
"name": "Conflict"
}
],
"input": {
"encoding": "application/json",
"schema": {
"properties": {
"decision": {
"enum": [
"approve",
"deny"
],
"type": "string"
},
"session": {
"description": "Provider session to grant to the device; required when `decision` is `approve`.",
"type": "unknown"
},
"userCode": {
"description": "The code the device displayed (case-insensitive).",
"type": "string"
}
},
"required": [
"userCode",
"decision"
],
"type": "object"
}
},
"output": {
"encoding": "application/json",
"schema": {
"properties": {
"ok": {
"type": "boolean"
},
"status": {
"type": "string"
}
},
"required": [
"ok",
"status"
],
"type": "object"
}
},
"type": "procedure"
}
},
"id": "dev.cocore.devicePair.confirm",
"lexicon": 1
}
Metadata
- DID
-
did:plc:5quuhkmwe2q4k3azfsgg7kdz - CID
-
bafyreicmkzd6mjahy3ewmc37lotqrnmzule7jlas3x3ivjy57l3xkptl24 - Indexed At
- 2026-06-21 00:58 UTC
- AT-URI
-
at://did:plc:5quuhkmwe2q4k3azfsgg7kdz/com.atproto.lexicon.schema/dev.cocore.devicePair.confirm
Similar Lexicons
Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Poll a device-pairing attempt by `deviceId`. While the user has not acted, returns `pending`. On approval, returns `session` together with the granted provider session. Terminal negative states are `denied`, `expired`, …
-
dev.cocore.devicePair.start procedure
Begin a device-pairing flow (OAuth 2.0 device-authorization style). Returns a `deviceId` plus a short human-typable `userCode` and the `verificationUri` where a signed-in user approves the pairing. The caller then polls…