List All Registered Permissions — GET /api/v1/permission

Returns every permission registered in the system, ordered ascending by idPermission. No role-permission check is applied — any authenticated user can call this endpoint. This is intentional so that administrators can browse available permissions when building role configurations.

Authentication

Requires a valid JWT in the Authorization header. No specific role permission is needed.

Request

Method: GET Path: /api/v1/permission

Headers

Authorization

string

required

Bearer token obtained from the login endpoint. Format: Bearer <token>

Response

200 OK

Returns all permission records in ascending idPermission order.

success

boolean

Always true for successful responses.

message

string

Human-readable status message. Value: "Permisos registados obtenidos".

data

array

Array of permission objects.

Show Permission object

idPermission

number

Unique numeric identifier for the permission.

nameUri

string

The route pattern this permission guards, e.g. GET /api/v1/users or DELETE /api/v1/roles/:idRole.

description

string

Human-readable description of what this permission allows.

Example Response

{
  "success": true,
  "message": "Permisos registados obtenidos",
  "data": [
    {
      "idPermission": 1,
      "nameUri": "GET /api/v1/users",
      "description": "List all users"
    },
    {
      "idPermission": 2,
      "nameUri": "POST /api/v1/roles",
      "description": "Create a new role"
    },
    {
      "idPermission": 3,
      "nameUri": "DELETE /api/v1/users/:id",
      "description": "Delete a user by ID"
    }
  ]
}

Error Responses

Status	Description
`401 Unauthorized`	Missing or invalid JWT token.

401 Unauthorized

{
  "success": false,
  "message": "No autorizado",
  "data": null
}

Code Example

cURL

curl -X GET http://localhost:3000/api/v1/permission \
  -H "Authorization: Bearer <your_token>"

Socket.IO Events

This is a read-only endpoint. A data:changed broadcast is not emitted. The requesting client receives operation:progress events for the permissions:fetchAll operation on their own socket only.

Event	Target	Operation	Status sequence
`operation:progress`	Requesting socket	`permissions:fetchAll`	`start` → `success`

Auth

Users

Roles

Permissions

Sidebar

List All Registered Permissions — GET /api/v1/permission

Authentication

Request

Headers

Response

200 OK

Error Responses

Code Example

Socket.IO Events

Build docs developers (and LLMs) love

Auth

Users

Roles

Permissions

Sidebar

Documentation Index

​Authentication

​Request

​Headers

​Response

​200 OK

​Error Responses

​Code Example

​Socket.IO Events

Build docs developers (and LLMs) love

Authentication

Request

Headers

Response

200 OK

Error Responses

Code Example

Socket.IO Events