app.didpic.identity.getSession
{
"$type": "com.atproto.lexicon.schema",
"defs": {
"main": {
"description": "Return the authenticated viewer's identity along with any opaque flags clients may use to gate UI.",
"output": {
"encoding": "application/json",
"schema": {
"properties": {
"avatarCid": {
"type": "string"
},
"did": {
"format": "did",
"type": "string"
},
"displayName": {
"type": "string"
},
"envAdmin": {
"description": "Implementation-defined flag. Clients should treat as opaque.",
"type": "boolean"
},
"handle": {
"format": "handle",
"type": "string"
},
"roles": {
"description": "Opaque flags assigned to the viewer. Values are implementation-defined; treat unknown entries as informational.",
"items": {
"type": "string"
},
"type": "array"
}
},
"required": [
"did",
"roles",
"envAdmin"
],
"type": "object"
}
},
"type": "query"
}
},
"id": "app.didpic.identity.getSession",
"lexicon": 1
}
Metadata
- DID
-
did:plc:an2jtp4jgkkbtmwfzhpbxawd - CID
-
bafyreif7ij5ia6ndcw5d3wchxjnn43at36r7x65ku5nlpnkyg7srpjpd4i - Indexed At
- 2026-05-17 07:18 UTC
- AT-URI
-
at://did:plc:an2jtp4jgkkbtmwfzhpbxawd/com.atproto.lexicon.schema/app.didpic.identity.getSession
Similar Lexicons
Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
chat.yakka.getSession query
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 `…
-
Describe the signed-in ILLI session: the account behind the illi_session cookie, which app it belongs to, and when the account joined the ILLI service. Served by the ILLI Service Node.
-
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…