Skip to main content
GET
/
api
/
v1
/
supportTickets
/
{ticketId}
/
Retrieve Support Ticket
curl --request GET \
  --url https://skala-sandbox.ripio.com/api/v1/supportTickets/{ticketId}/ \
  --header 'Authorization: Bearer <token>'
{
  "ticketId": "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d",
  "status": "CREATED",
  "issueKey": "SUP-1234"
}
The recommended way to learn a ticket’s outcome is to subscribe to the Support Ticket webhook events, which notify your application automatically as soon as a ticket reaches the CREATED or FAILED status. You can also check a specific ticket’s status on demand with this endpoint.
Support tickets are an opt-in feature that must be enabled for your account by the Ripio team. While the feature is disabled, this endpoint returns 403 Forbidden with the error code 20061 (SupportTicketsNotEnabledException). Contact the Ripio team to have it enabled.

​
Checking a ticket’s status

Use this endpoint to look up the current status of a ticket created via Create Support Ticket, passing the ticketId returned there. The status field follows this lifecycle:
statusMeaning
PENDINGThe ticket was accepted and is still being processed. issueKey is null.
CREATEDThe ticket was successfully registered with Ripio’s support team. issueKey is populated.
FAILEDThe ticket could not be registered. issueKey is null.

Authorizations

​
Authorization
string
header
required

Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>.

Path Parameters

​
ticketId
string<uuid>
required

The ticketId returned by the Create Support Ticket endpoint.

Response

Current state of the support ticket.

​
ticketId
string<uuid>
required

Ripio's identifier for the support ticket. Use it to correlate the Support Ticket webhook events, or to look up the ticket's status on demand via the Retrieve Support Ticket endpoint.

​
status
enum<string>
required

Lifecycle status of the ticket. PENDING: accepted and being processed (no reference yet). CREATED: successfully registered in Ripio's support system; issueKey is populated. FAILED: the ticket could not be registered.

Available options:
PENDING,
CREATED,
FAILED
​
issueKey
string | null
required

Human-readable reference of the ticket in Ripio's support system (e.g. SUP-1234). null until the ticket reaches the CREATED status.