Skip to main content
GET
/
api
/
catalogos
/
areas
Get Areas
curl --request GET \
  --url https://api.example.com/api/catalogos/areas
{
  "Id": 123,
  "Nombre": "<string>",
  "Activo": true
}

Overview

This endpoint returns all areas in the system. Areas are used to categorize tickets by department or functional area (e.g., IT, HR, Finance). This catalog data is typically used to populate dropdown menus in ticket creation forms.

Endpoint

GET /api/catalogos/areas

Response

Returns an array of area objects.
Id
integer
required
Unique identifier for the area
Nombre
string
required
Name of the area (e.g., “IT”, “Human Resources”, “Finance”)
Activo
boolean
required
Indicates whether the area is active and available for selection

Response Example

[
  {
    "id": 1,
    "nombre": "Tecnología de la Información",
    "activo": true
  },
  {
    "id": 2,
    "nombre": "Recursos Humanos",
    "activo": true
  },
  {
    "id": 3,
    "nombre": "Finanzas",
    "activo": true
  },
  {
    "id": 4,
    "nombre": "Operaciones",
    "activo": false
  }
]

Request Example

curl -X GET "http://localhost:5000/api/catalogos/areas" \
  -H "Content-Type: application/json"

Usage Notes

Filter for active areas (activo: true) when displaying options to users in dropdown menus. Inactive areas are typically kept in the database for historical reference but should not be selectable for new tickets.

Build docs developers (and LLMs) love