Sluby
REST APIAuth

Use an invite or reset link, and sign in.

An invite makes a new member with its role. A reset link sets the member’s password (their first, when they had none) and ends every other session of the account. Either way the link is used up and the browser is signed in.

POST
/api/v1/auth/invites/{token}/accept

An invite makes a new member with its role. A reset link sets the member’s password (their first, when they had none) and ends every other session of the account. Either way the link is used up and the browser is signed in.

Path Parameters

token*string

The token from the invite or reset link.

Request Body

application/json
  1. body

For an invite: name, email and password, making a new member. For a reset link: password, plus email when the member has no password yet.

name*string
Length1 <= length <= 100
email*string
Lengthlength <= 254
password*string
Length10 <= length <= 256

Response Body

Password set from a reset link, signed in.

application/json
  1. response
success*unknown
Example Request
curl -X POST 'https://sluby.example.com/api/v1/auth/invites/string/accept' \  -H 'Content-Type: application/json' \  -d '{  "name": "string",  "email": "string",  "password": "stringstri"}'
Example Response
{  "success": true}

What an invite or reset link is for. GET

Public: the join and reset pages call it with the token from their url. 30 link requests per client address in 10 minutes.

The signed-in account. GET

The account id and display name, plus the provider, provider label and handle the browser signed in with, its role, every way it signs in (`sign_in`), and the session expiry. With AUTH_DISABLED it is the local dev account (`provider: "local"`, `auth_disabled: true`, `role: "admin"`).