> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Obtenir un rôle

> GET /multi-users/access-levels/{pk}/

Récupère un seul rôle (niveau d'accès) sur l'hôte de l'**API de gestion** (`api.scanova.io`), authentifié avec votre clé brute d'API de gestion.

```
GET https://api.scanova.io/multi-users/access-levels/{pk}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="pk" type="integer" required>
  L'`id` du rôle, depuis [Lister les rôles](/fr/api-reference/management-api/shared-users/roles-list).
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/multi-users/access-levels/3/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 3,
    "name": "Viewer",
    "slug": "viewer",
    "permissions": [
      { "id": 23, "code": "QR_CODE_CAN_VIEW", "name": "Can view QR Code", "description": "Allows viewing QR code details.", "is_boolean": true }
    ],
    "is_custom": false
  }
  ```
</ResponseExample>

Visible : les rôles personnalisés propres au compte, plus tous les rôles système (`is_custom: false`) — ceux-ci sont partagés entre tous les comptes, pas seulement celui-ci.

## Voir aussi

* [Lister les rôles](/fr/api-reference/management-api/shared-users/roles-list) — trouver un `id` de rôle.
* [Mettre à jour un rôle personnalisé](/fr/api-reference/management-api/shared-users/roles-update) — modifier ce rôle, s'il appartient au compte.
* [Supprimer un rôle personnalisé](/fr/api-reference/management-api/shared-users/roles-delete) — supprimer ce rôle, s'il appartient au compte.
* [Présentation de l'API de gestion](/fr/api-reference/management-api/overview) — le schéma d'authentification et les règles de quota applicables à cet endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /multi-users/access-levels/{pk}/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /multi-users/access-levels/{pk}/:
    get:
      summary: Retrieve a role
      operationId: getManagedAccessLevel
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      responses:
        '200':
          description: >-
            One role, with its permission set. Visible: the account's own custom
            roles, plus every system role.
          content:
            application/json:
              example:
                id: 3
                name: Viewer
                slug: viewer
                permissions:
                  - id: 23
                    code: QR_CODE_CAN_VIEW
                    name: Can view QR Code
                    description: Allows viewing QR code details.
                    is_boolean: true
                is_custom: false
        '404':
          description: >-
            No role with this id, or a custom role belonging to a different
            account.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your Management API key as the raw value of the Authorization
        header — no "Bearer " or "Token " prefix, and no other characters.
        Example: `Authorization: 401f7ac837da42b97f613d789819ff93537bee6a`. A
        header containing more than one space-separated part is rejected
        outright. Requests also require the request's Host header to be the
        management API host (e.g. api.scanova.io) — the same key sent to the
        regular API host will not authenticate.

````