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

Overview

This endpoint returns all priority levels in the system. Priorities define the urgency and importance of tickets, with associated numeric levels for sorting and escalation. This catalog data is used to populate priority selection dropdowns in ticket management interfaces.

Endpoint

GET /api/catalogos/prioridades

Response

Returns an array of priority objects.
Id
integer
required
Unique identifier for the priority level
Nombre
string
required
Name of the priority level (e.g., “Low”, “Medium”, “High”, “Critical”)
Nivel
integer
required
Numeric level associated with the priority. Higher values typically indicate greater urgency or importance. Used for sorting and escalation logic.

Response Example

[
  {
    "id": 1,
    "nombre": "Baja",
    "nivel": 1
  },
  {
    "id": 2,
    "nombre": "Media",
    "nivel": 2
  },
  {
    "id": 3,
    "nombre": "Alta",
    "nivel": 3
  },
  {
    "id": 4,
    "nombre": "Crítica",
    "nivel": 4
  }
]

Request Example

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

Usage Notes

The Nivel field is crucial for implementing priority-based sorting and filtering. When displaying tickets, you can sort by this field to show highest priority items first. Business rules and SLA calculations often depend on priority levels.

Common Use Cases

  • Ticket Creation: Display priorities in dropdown for users to select ticket urgency
  • Ticket Filtering: Allow users to filter tickets by priority level
  • Sorting: Sort ticket lists by priority level (highest to lowest)
  • SLA Management: Different priorities may have different response time requirements
  • Escalation Rules: Automatically escalate tickets above certain priority levels

Build docs developers (and LLMs) love