Skip to main content
This is a public endpoint. No authentication token is required. It is intended for end-users to check the status of a ticket they submitted.

Request

POST /api/tickets/consultar You must supply the ticket label (given to the user at creation time) and the email address used when the ticket was submitted. Both values are required for verification.

Body parameters

label
string
required
The ticket reference label returned when the ticket was created (e.g. TKT-2026-00042).
email
string
required
The email address of the requester. Must match the email recorded on the ticket.

Response

Returns a 200 OK with the full ticket detail object.
ticketUuid
string
required
Internal UUID of the ticket.
ticketLabel
string
required
Human-readable ticket reference.
ticketNum
number
Sequential ticket number, if assigned.
solicitanteNombre
string
required
Full name of the requester.
solicitanteEmail
string
required
Email address of the requester.
solicitanteTel
string
Phone number of the requester, if provided.
tieneWhatsapp
boolean
required
Whether the phone number has WhatsApp enabled.
documento
string
Identity document number of the requester, if provided.
empresaDepartamento
string
Company or department, if provided.
tipoSolicitud
string
Request type (e.g. INCIDENTE, QUEJA).
categoria
string
required
Category the ticket was filed under.
subcategoria
string
Subcategory, if provided.
asunto
string
Short subject line, if provided.
descripcionProblema
string
required
Full description of the request or issue as submitted.
respuestaCliente
string
Agent response visible to the requester, if one has been recorded.
areaAsignada
string
Area the ticket is currently assigned to.
prioridadNombre
string
Current priority level name.
estadoNombre
string
Current status name.
creadoEn
string
ISO 8601 timestamp of when the ticket was created.
actualizadoEn
string
ISO 8601 timestamp of the last update.

Latest history entry

The following fields reflect the most recent action recorded in the ticket’s history log.
ultimaFechaHistorial
string
ISO 8601 timestamp of the most recent history entry.
ultimaAccion
string
Action code of the most recent history entry (e.g. CAMBIO_ESTADO, RESPUESTA).
ultimoMotivo
string
Reason or note recorded with the most recent history entry.
ultimoActorNombre
string
Full name of the agent who performed the most recent action.
ultimoActorRol
string
Role of the agent who performed the most recent action.
estadoAntes
string
Status before the most recent change, if applicable.
estadoDespues
string
Status after the most recent change, if applicable.
prioridadAntes
string
Priority before the most recent change, if applicable.
prioridadDespues
string
Priority after the most recent change, if applicable.
areaAntes
string
Assigned area before the most recent change, if applicable.
areaDespues
string
Assigned area after the most recent change, if applicable.

Error codes

StatusDescription
400Invalid request body — missing fields or invalid email format.
404No ticket found matching the provided label and email combination.
curl --request POST \
  --url https://api.example.com/api/tickets/consultar \
  --header 'Content-Type: application/json' \
  --data '{
    "label": "TKT-2026-00042",
    "email": "[email protected]"
  }'
{
  "ticketUuid": "e3b2c1d4-5a6f-7890-abcd-ef1234567890",
  "ticketLabel": "TKT-2026-00042",
  "ticketNum": 42,
  "solicitanteNombre": "Ana García",
  "solicitanteEmail": "[email protected]",
  "solicitanteTel": "3001234567",
  "tieneWhatsapp": true,
  "documento": null,
  "empresaDepartamento": "Recursos Humanos",
  "tipoSolicitud": "INCIDENTE",
  "categoria": "Sistemas",
  "subcategoria": "Correo electrónico",
  "asunto": "No puedo acceder al correo corporativo",
  "descripcionProblema": "Desde esta mañana no puedo iniciar sesión en el correo corporativo. El sistema muestra error 403.",
  "respuestaCliente": "Hemos escalado el caso al equipo de infraestructura. Le notificaremos en breve.",
  "areaAsignada": "TECNOLOGIA",
  "prioridadNombre": "ALTA",
  "estadoNombre": "EN_PROCESO",
  "creadoEn": "2026-03-24T09:15:00Z",
  "actualizadoEn": "2026-03-24T10:30:00Z",
  "ultimaFechaHistorial": "2026-03-24T10:30:00Z",
  "ultimaAccion": "CAMBIO_ESTADO",
  "ultimoMotivo": "Escalado a infraestructura",
  "ultimoActorNombre": "Carlos Méndez",
  "ultimoActorRol": "MESA",
  "estadoAntes": "ABIERTO",
  "estadoDespues": "EN_PROCESO",
  "prioridadAntes": null,
  "prioridadDespues": null,
  "areaAntes": "MESA",
  "areaDespues": "TECNOLOGIA"
}

Build docs developers (and LLMs) love