Your account

GET

/auth/account

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

• Production
• Staging

The person behind the session: their email and name, the sign-in methods linked to the account, and every session they hold — this one flagged. One row per browser: a CRM tab’s own session belongs to the browser session it was minted from, ends with it, and is not listed apart. Session only.

Authorizations

• sessionAuth

Responses

200

The account.

Media typeapplication/json

object

user

required

object

id

required

string

email

required

string

name

required

string

methods

required

Array<object>

object

provider

required

zoho-<dc> for a Zoho sign-in linked to this account. A magic link needs no linked provider and is always available to the email.

string

linkedAt

required

string

sessions

required

Array<object>

object

id

required

string

current

required

boolean

createdAt

required

string

lastUsedAt

required

When the session last slid its expiry.

string

expiresAt

required

string

ipAddress

required

string | null

userAgent

required

string | null

orgId

required

The org the session is working in, if any.

string | null

staffView

required

A Sloose staff member’s time-boxed view of an org as this person. Listed so it is seen; it ends by its own clock, or when the person ends it here, since it acts as them.

boolean

Example

{
  "methods": [
    {
      "provider": "zoho-au"
    }
  ]
}

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"
}