FerryDocs
ReferenceAPI overview

Account endpoints

The endpoints below /api/v1/auth control the account. An API token cannot use them.

Edit on GitHub
Callerno proof yet/api/v1/authsetup, login, cli

Six endpoints need no authentication. A browser or a terminal calls them before it has a proof.

1 / 3

All that controls the account is below /api/v1/auth. The API reference describes each .

No authentication

EndpointWhat it does
GET /api/v1/auth/statusAnswers {setup_required, auth, user}. See below.
POST /api/v1/auth/setupCreates the account from {email, password, code} and signs the browser in (201). code is the setup code.
POST /api/v1/auth/loginSigns in with {email, password}. The answer sets the session cookie.
POST /api/v1/auth/logoutSigns out.
POST /api/v1/auth/cliStarts a ferry login.
POST /api/v1/auth/cli/{id}/tokenThe terminal calls it again and again until its ferry login has an answer.

Session only

EndpointWhat it does
POST /api/v1/auth/passwordChanges the password.
GET /api/v1/auth/sessionsLists the sessions.
DELETE /api/v1/auth/sessions/{id}Ends a session: that browser signs out.
GET /api/v1/auth/tokensLists the API tokens.
POST /api/v1/auth/tokensCreates an API token. expires_in_days is optional, from 1 to 3650.
DELETE /api/v1/auth/tokens/{id}Revokes an API token.
GET /api/v1/auth/cli/{id}Shows a ferry login request.
POST /api/v1/auth/cli/{id}/approveApproves it.
POST /api/v1/auth/cli/{id}/denyDenies it.

On this page