A valid request URL is required to generate request examples{
"data": {
"actorId": "user-camille",
"identity": {
"id": "user-camille",
"name": "Camille Roy",
"email": "camille.roy@rivoli-retail.fr",
"role": "cashier",
"store": "Boutique Rivoli",
"active": true
},
"effectivePermissions": [
"pos.catalog.view",
"pos.checkout.operate"
]
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123,
"fieldErrors": [
{
"field": "<string>",
"message": "<string>"
}
]
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}Resolve the authenticated actor's identity and effective POS scopes (MCP gateway alias)
Compatibility alias of GET /v1/auth/whoami mounted at /api/auth/whoami for the solya-api-mcp gateway, which hardcodes that path for its permission-aware discovery. It is IDENTICAL to the canonical operation in every respect — same authentication, same (empty) scope requirement, and the same { data: { actorId, identity, effectivePermissions } } envelope served from the same handler. When driving the API yourself, call GET /v1/auth/whoami directly (see it for the full contract); this path exists only for the gateway.
A valid request URL is required to generate request examples{
"data": {
"actorId": "user-camille",
"identity": {
"id": "user-camille",
"name": "Camille Roy",
"email": "camille.roy@rivoli-retail.fr",
"role": "cashier",
"store": "Boutique Rivoli",
"active": true
},
"effectivePermissions": [
"pos.catalog.view",
"pos.checkout.operate"
]
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123,
"fieldErrors": [
{
"field": "<string>",
"message": "<string>"
}
]
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}{
"error": {
"code": "VALIDATION_FAILED",
"message": "<string>",
"statusCode": 123
}
}Authorizations
Authorization: Bearer <token>. Accepts EITHER a Keycloak access token (scopes-in-token) OR an opaque POS session token; both resolve to the same pos.* scope vocabulary the route guards enforce.
Response
The caller's own directory identity (or null) plus their effective POS scopes, sorted and de-duplicated, under a data envelope.
The caller's own directory identity (or null) plus their effective POS scopes, sorted and de-duplicated, under a data envelope.
Show child attributes
Show child attributes