Skip to main content
Two endpoints are available for reading module data. Neither requires a specific permission beyond a valid Bearer token.

​
Authentication

Requires a valid Bearer token. 
Authorization: Bearer <token>

​
GET /api/Modulo

Returns an array of all modules registered in the system.

​
Response fields

​
[]
ModuloModel[]
Array of module objects.

​
Examples

curl --request GET \
  --url https://your-api-host/api/Modulo \
  --header 'Authorization: Bearer <token>'

[
  {
    "IdModulo": 1,
    "strNombreModulo": "Usuarios",
    "Ruta": "/Module/Usuario",
    "Clave": "usuario"
  },
  {
    "IdModulo": 2,
    "strNombreModulo": "Perfiles",
    "Ruta": "/Module/Perfil",
    "Clave": "perfil"
  },
  {
    "IdModulo": 3,
    "strNombreModulo": "Reportes",
    "Ruta": "/Module/Reporte",
    "Clave": "reporte"
  }
]

​
GET /api/Modulo/

Returns a single module by its ID. Returns 404 Not Found if no module with that ID exists.

​
Path parameters

​
id
integer
required
ID of the module to retrieve.

​
Response fields

​
IdModulo
integer
required
Module ID.
​
strNombreModulo
string
required
Display name shown in the UI.
​
Ruta
string
required
Frontend route for this module.
​
Clave
string
required
Unique key used as the prefix in permission strings.

​
Examples

curl --request GET \
  --url https://your-api-host/api/Modulo/1 \
  --header 'Authorization: Bearer <token>'

{
  "IdModulo": 1,
  "strNombreModulo": "Usuarios",
  "Ruta": "/Module/Usuario",
  "Clave": "usuario"
}

Build docs developers (and LLMs) love

Get started for freeTalk to us