Skip to main content
This endpoint requires authentication. Only users with the ADMIN, MESA, or AREA role may access it. AREA agents can only update tickets assigned to their own area.

Request

POST /api/tickets/{ticket_id}/actualizar The actor’s identity (id, nombre, email, rol) is read automatically from your JWT token and recorded in the ticket history. You do not pass actor information in the request body.

Path parameters

ticket_id
string
required
UUID of the ticket to update (e.g. e3b2c1d4-5a6f-7890-abcd-ef1234567890).

Body parameters

estado
string
required
New status for the ticket. Between 3 and 50 characters (e.g. EN_PROCESO, CERRADO, RESUELTO).
prioridad
string
required
New priority level name. Between 3 and 50 characters (e.g. ALTA, MEDIA, BAJA).
area
string
required
Area to assign the ticket to. Between 2 and 100 characters (e.g. TECNOLOGIA, MESA).
respuesta
string
required
Agent response or note to record on the ticket. Minimum 5 characters. This text is visible to the requester when they look up their ticket.

Response

Returns a 200 OK with a confirmation message.
message
string
required
Always returns "Ticket actualizado correctamente" on success.

Error codes

StatusDescription
400Invalid request body — validation failed (e.g. respuesta too short, field missing).
401Missing or invalid authentication token.
403Your role does not permit access, or (for AREA agents) the ticket is assigned to a different area.
404No ticket found with the specified UUID.
curl --request POST \
  --url https://api.example.com/api/tickets/e3b2c1d4-5a6f-7890-abcd-ef1234567890/actualizar \
  --header 'Authorization: Bearer <your_token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "estado": "RESUELTO",
    "prioridad": "ALTA",
    "area": "TECNOLOGIA",
    "respuesta": "Se restableció el acceso al correo corporativo. El problema fue causado por un certificado expirado que ya fue renovado."
  }'
{
  "message": "Ticket actualizado correctamente"
}

Build docs developers (and LLMs) love