EVeveryinfra
Support

A support ticket and its messages

Status, what happens next and the latest 100 messages of one ticket. A key can always read the tickets it opened itself; reading the account's other tickets (opened in the console or with other keys) needs the support:read account scope, which the account owner enables under API Keys in the console. Anything else is 404 ticket_not_found. Not charged; counted in the 60 account requests per minute. The MCP tool everyinfra_get_ticket (argument ticket_id) follows the same rules and returns the same object.

get/api/v1/support/tickets/{ticket_id}

Request

  • Base URL
    https://api.everyinfra.com
  • URL
    https://api.everyinfra.com/api/v1/support/tickets/{ticket_id}
  • Auth
    HTTP bearer

Path parameters

ticket_idinteger required

The ticket number returned when it was opened

Response

The ticket

object'support_ticket'
ticket_idinteger

The ticket number (#N in the console and in emails)

urlstring

The ticket in the console, for the account owner

subjectstring
status'new' | 'in_progress' | 'waiting_customer' | 'investigating' | 'resolved' | 'closed' nullable
status_textstring
resolution_pendingboolean

Support asked the account owner to confirm the problem is solved

category'general' | 'product' | 'integration' | 'billing' | 'order' | 'incident' nullable

The ticket's category as support files it

created_atstring date-time nullable
updated_atstring date-time nullable
next_stepstring

What happens next and what to do, in one sentence

support_hoursstring
messages_truncatedboolean

Changes

No recorded changes to this operation across all 16 revisions of this API.