Invitations waiting for you

GET

/auth/invitations

curl --request GET \
  --url https://api.sloose.com/auth/invitations \
  --header 'Authorization: Bearer <token>'

• Production
• Staging

The invitations to the address this session signed in with, across every org: pending, not past their time, and to an org still open — newest first. The org and the inviter are named as the invitation’s mail names them.

Session only, and not a staff member’s view of an org: these are the person’s, not the org’s the view was opened on.

Authorizations

• sessionAuth

Responses

200

Waiting, newest first.

Media typeapplication/json

object

invitations

required

Array<object>

object

id

required

string

orgId

required

string

orgName

required

The org’s name, or “a team” when it could be read as coming from Sloose.

string

role

required

string

Allowed values: operator builder admin

invitedBy

required

The inviter’s name, or “Someone at …” when it could be read as coming from Sloose or the inviter has gone.

string

invitedAt

required

string

expiresAt

required

string

Example

{
  "invitations": [
    {
      "role": "operator"
    }
  ]
}

401

No bearer, or one that is expired, revoked or no longer resolves to a member.

Media typeapplication/json

The error envelope every non-2xx answer uses.

object

error

required

Human-readable explanation.

string

code

Machine-readable reason. Absent on a few legacy 400s.

string

key

additional properties

Example^generated

{
  "error": "example",
  "code": "example"
}

403

An API token was used (code: SESSION_REQUIRED), or the session is a staff member’s view of an org (code: STAFF_VIEW).

Media typeapplication/json

The error envelope every non-2xx answer uses.

object

error

required

Human-readable explanation.

string

code

Machine-readable reason. Absent on a few legacy 400s.

string

key

additional properties

Example^generated

{
  "error": "example",
  "code": "example"
}