chat.yakka.getSession

yakka.chat

{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "Who the caller is signed in as. The session cookie carries an opaque id and nothing else (ADR 0034 §2), so this is how a client learns its own DID — it cannot read one out of the cookie, by design. Answers 200 with `signedIn: false` rather than 401 for an anonymous caller: not being signed in is an ordinary state of the application, not an error in the request.",
      "output": {
        "encoding": "application/json",
        "schema": {
          "ref": "#output",
          "type": "ref"
        }
      },
      "type": "query"
    },
    "output": {
      "properties": {
        "signedIn": {
          "type": "boolean"
        },
        "viewer": {
          "ref": "chat.yakka.defs#memberView",
          "type": "ref"
        }
      },
      "required": [
        "signedIn"
      ],
      "type": "object"
    }
  },
  "id": "chat.yakka.getSession",
  "lexicon": 1
}

Validate Record

Validate a record against chat.yakka.getSession

Validation Options
Automatically resolve and include external schemas for full validation
Treat any remaining unresolved references as valid

Metadata

DID
did:plc:wpjoy2orkqq5m65vq7gg7liz
CID
bafyreifnckbdnrfolqmxvjappb4yd2thgaybq6qcobq4k7df7a7564yega
Indexed At
2026-08-29 15:21 UTC
AT-URI
at://did:plc:wpjoy2orkqq5m65vq7gg7liz/com.atproto.lexicon.schema/chat.yakka.getSession

Referenced Schemas (1)

Similar Lexicons

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Return the authenticated viewer's identity along with any opaque flags clients may use to gate UI.

  • Get the authenticated user's lsky-specific state: profile, onboarding status. The user's DID and handle are resolved from the inter-service auth JWT. This is the first call the app should make after login to hydrate lsk…

  • Get information about the current auth session. Requires auth.

Lexicon Garden

@