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

​
Overview

This endpoint returns all possible states in the ticket lifecycle. States represent the current status of a ticket (e.g., Open, In Progress, Resolved, Closed). The Final property indicates whether a state represents a terminal status, which is useful for workflow validation and reporting.

​
Endpoint

GET /api/catalogos/estados

​
Response

Returns an array of ticket state objects.
​
Id
integer
required
Unique identifier for the ticket state
​
Nombre
string
required
Name of the state (e.g., “Open”, “In Progress”, “Resolved”, “Closed”)
​
Final
boolean
required
Indicates whether this is a final/terminal state. When true, the ticket has reached the end of its lifecycle and typically cannot transition to other states. Used for completion metrics and workflow validation.

​
Response Example

[
  {
    "id": 1,
    "nombre": "Abierto",
    "final": false
  },
  {
    "id": 2,
    "nombre": "En Progreso",
    "final": false
  },
  {
    "id": 3,
    "nombre": "En Espera",
    "final": false
  },
  {
    "id": 4,
    "nombre": "Resuelto",
    "final": true
  },
  {
    "id": 5,
    "nombre": "Cerrado",
    "final": true
  },
  {
    "id": 6,
    "nombre": "Cancelado",
    "final": true
  }
]

​
Request Example

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

​
Usage Notes

Final States: States where Final: true represent completed tickets. These are important for:
  • Preventing further updates to closed tickets
  • Calculating completion metrics and KPIs
  • Filtering active vs. completed work
  • Generating reports on resolved issues

​
Common Use Cases

  • State Transition Dropdowns: Display available states when updating a ticket
  • Workflow Validation: Prevent transitions from final states or enforce valid state flows
  • Active Ticket Filters: Show only tickets where Final: false for active work queues
  • Completion Metrics: Calculate resolution rates using tickets in final states
  • Status Tracking: Visualize ticket progress through workflow stages
  • Automated Workflows: Trigger notifications or actions when tickets enter final states

Build docs developers (and LLMs) love

Get started for freeTalk to us