com.atproto.server.createSession
Create an authentication session.
Details · procedure
| Kind | procedure |
|---|---|
| Authority | server.atproto.com |
| Indexed |
Procedure
procedure · POSTInput
application/jsonallowTakendown
booleanWhen true, instead of throwing error for takendown accounts, a valid response with a narrow scoped token will be returned
authFactorToken
stringHandle or other identifier supported by the server for the authenticating user.
Output
application/jsonactive
booleandidDoc
unknownemailAuthFactor
booleanemailConfirmed
booleanstatus
stringIf active=false, this optional field indicates a possible reason for why the account is not active. If active=false and no status is supplied, then the host makes no claim for why the repository is no longer being hosted.
knownValues: takendown | suspended | deactivated
Errors
AccountTakedown
No description in schema.
AuthFactorTokenRequired
No description in schema.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
com.atproto.server.refreshSession
procedureRefresh an authentication session. Requires auth using the 'refreshJwt' (not the 'accessJwt').
-
Get information about the current auth session. Requires auth.
-
Create an account on behalf of a client attested by a trusted issuer. Authenticated with a service-auth JWT (iss = trusted issuer DID, aud = this PDN, lxm = this method, exp - iat <= 60 s, unique jti). No invite code, no captcha. Without handle the server generates a memorable one; without email the server stores the placeholder <label>@newnal.id. Returns a full session, like createAccount; clients that need a scoped session create a scoped app password with it.
-
Start a Social Dept. session for the account that signed the service auth token sent as the bearer credential. The token's lxm must be this method.
-
at.blueharbor.createSession
procedureThe lxm named in service-auth JWTs minted for the BlueHarbor backend (aud did:web:blueharbor.at). The backend verifies the JWT against the caller's DID document and exchanges it for a BlueHarbor session token. Defined here so the method identifier resolves; the HTTP call itself is served by the BlueHarbor service, not a PDS.