The caller's own operator profile

GET

/operator/me

const url = 'http://localhost:3000/operator/me';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url http://localhost:3000/operator/me \
  --header 'Authorization: Bearer <token>'

Authorizations

operatorToken

Responses

200

Same shape as login and invite acceptance — id, name, email, role, tenant_id.

application/json

An operator as returned by login, invite acceptance, and GET /operator/me — the same shape everywhere so a dashboard hitting any of the three sees one model. Never carries password_hash.

object

required

string

name

required

string

email

required

string format: email

role

required

string

Allowed values: staff owner member

tenant_id

required

Null for platform staff.

string | null

Example

{
  "role": "staff"
}

401

Invalid, expired, revoked, or absent token.

application/json

object

error

required

object

code

required

string

Allowed values: VALIDATION_FAILED UNAUTHENTICATED FORBIDDEN NOT_FOUND CONFLICT RATE_LIMITED INTERNAL

message

required

string

requestId

required

string

fields

Present only for VALIDATION_FAILED.

Array<object>

object

path

string

message

string

Example

{
  "error": {
    "code": "VALIDATION_FAILED"
  }
}