Get support report
get_support_ticketRead one support report in full: status, the answers it was filed with and the conversation with Skydropx support (newest 50 messages), where list_support_tickets gives only summaries. Scoped to the connected Skydropx account.
It only reads: the thread is not marked seen (support_replied_since_last_visit keeps its value until the report is opened in the app or answered with reply_support_ticket) and nothing is synced with support's helpdesk; the answer is what is stored, so a reply that just arrived shows after the next sync. An unknown id or folio, or another account's, returns error code NOT_FOUND.
Check can_reply before reply_support_ticket; reply_reopens says replying reopens a finished report. Returns the report summary plus answers, can_reply, reply_reopens and messages.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>"
},
"name": "get_support_ticket"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The report's id (UUID) or its folio, from list_support_tickets or create_support_ticket; right after filing the folio is still empty, so use the id |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Report id (UUID), for get_support_ticket / reply_support_ticket | |
| type | No | Report type key (see list_support_ticket_types) | |
| folio | No | Support's folio, which the user sees; null for a few seconds after filing | |
| status | No | Stage: created, progress, action (support waits for the user), finished, indemnified or reopened | |
| answers | No | The form the report was filed with | |
| subject | No | Title the user sees in their list | |
| messages | No | The conversation, oldest first | |
| shipment | No | The shipment the report is about; null for a general report | |
| can_reply | No | Whether reply_support_ticket accepts a message | |
| proactive | No | true for a case support opened for the user | |
| type_name | No | Report type, human-readable | |
| created_at | No | ||
| updated_at | No | ||
| reply_reopens | No | Whether replying reopens this finished report | |
| support_replied_since_last_visit | No | true when support answered after the user last opened the thread |