Skip to main content

​
GET /api/v1/tickets/

Retrieves complete information about a technical support ticket using its unique ID. This endpoint extracts essential elements such as the opening date, assigned priority, and checks the history to retrieve the latest response or current resolution status recorded in the external system.

​
Path Parameters

​
ticket_id
integer
required
The unique identifier of the ticket to retrieve

​
Response

The endpoint returns a BackendResponse wrapper with the following structure:
​
ok
boolean
Indicates if the request was successful
​
type
string
Response type: success or info
​
action
string
Action identifier for the response. Possible values:
  • ticket_found - Ticket successfully retrieved
  • ticket_not_found - No ticket exists with the provided ID
​
data
object | null
The ticket data object when found, or null if not found
​
message
string | null
Optional message providing additional context
​
meta
object | null
Optional metadata
curl -X GET https://api.wisphub.net/api/v1/tickets/50

​
Example Responses

{
  "ok": true,
  "type": "success",
  "action": "ticket_found",
  "data": {
    "ticket_id": 50,
    "subject": "Falla Masiva",
    "created_at": "2026-02-26 10:00",
    "end_date": "2026-02-28 10:00",
    "status_ticket": "Abierto",
    "priority": "3",
    "answer_text": null
  },
  "message": null,
  "meta": null
}

​
Response Handling

The response always has ok: true even when a ticket is not found. Check the action field to determine if the ticket exists:
  • ticket_found: Ticket data is available in the data field
  • ticket_not_found: The data field will be null

​
Ticket Status Values

The status_ticket field represents the current state of the ticket. Common values include:
  • Abierto: Newly created, awaiting assignment or action
  • En Progreso: Actively being worked on by a technician
  • Cerrado: Resolved and closed
The specific status values may vary based on your WispHub configuration.

​
Resolution Date Calculation

The end_date field represents the estimated or actual resolution date:
  • Automatically calculated when a ticket is created
  • Based on MAX_TICKET_RESOLUTION_DAYS setting (default: 3 business days)
  • Excludes weekends and holidays from the calculation
  • May be updated when ticket status changes