---
title: "Resolve signed-in account role"
method: GET
path: "/v1/account/context"
tags: ["Customer Account"]
---

# Resolve signed-in account role

`GET /v1/account/context`

## Request

- Base URL: `https://loppee.com`
- URL: `https://loppee.com/v1/account/context`
- Auth: HTTP bearer

Returns the active role and workspace for the signature-verified human session, plus two-factor routing hints (is an authenticator enrolled; must this session step up before role endpoints answer). It exposes no account identifiers or PII and never weakens role-specific MFA gates — clients route on the hints, the role endpoints still enforce.

## Response `200`

Resolve signed-in account role response

- object
  - `schema_version` '0.2', required
  - `role` 'customer' | 'owner' | 'admin' | 'null', nullable, required
  - `status` 'active' | 'not_created', required
  - `workspace` 'customer' | 'owner' | 'admin' | 'none', required
  - `role_exclusive` true, required
  - `mfa_enrolled` boolean, nullable, required
  - `step_up_required` boolean, nullable, required

## Other responses

- `401`: ErrorResponse
- `403`: ErrorResponse
- `404`: ErrorResponse
- `429`: RateLimitError
- `default`: ErrorResponse

---

[API](https://skmtc.dev/loppee/apis/loppee-business-registry-api-for-external-agents.md) · [All operations](https://skmtc.dev/loppee/apis/loppee-business-registry-api-for-external-agents/llms.txt) · [OpenAPI document](https://skmtc.dev/loppee/apis/loppee-business-registry-api-for-external-agents/revisions/37285f7cddcd?raw)