Support
Replies List
https://api.linode.com/v4/support/tickets/{ticketId}/repliesReturns a collection of replies to a Support Ticket on your Account.
Path Parameters
The ID of the Support Ticket.
Query Parameters
The page of a collection to return.
The number of items to return per page.
Request Samples
- Shell
- CLI
curl -H "Authorization: Bearer $TOKEN" \
https://api.linode.com/v4/support/tickets/11223344/replies
Response Samples
- 200
- default
{
"data": [
{
"id": "",
"created": "2015-06-02T14:31:41",
"description": "Hello,\\nI'm sorry to hear that you are having trouble resetting the root password of your Linode. Just to be sure, have you tried to follow the instructions in our online documentation? The link is here:\\n \\nhttps://linode.com/docs/guides/reset-the-root-password-on-your-linode/ \\n\\nIf you have, please reply with any additional steps you have also taken.\\n\\nRegards, Linode Support Team\n",
"created_by": "John Q. Linode",
"gravatar_id": "474a1b7373ae0be4132649e69c36ce30",
"from_linode": true
}
],
"page": 1,
"pages": 1,
"results": 1
}Responses
200: Returns a paginated list of SupportTicketReply objects.
The unique ID of this Support Ticket reply.
The date and time this Ticket reply was created.
The body of this Support Ticket reply.
The User who submitted this reply.
The Gravatar ID of the User who created this reply.
If set to true, this reply came from a Linode employee.
The current page.
The total number of pages.
The total number of results.
default: Error
What happened to cause this error. In most cases, this can be fixed immediately by changing the data you sent in the request, but in some cases you will be instructed to open a Support Ticket or perform some other action before you can complete the request successfully.
The field in the request that caused this error. This may be a path, separated by periods in the case of nested fields. In some cases this may come back as "null" if the error is not specific to any single element of the request.
Reply Create
https://api.linode.com/v4/support/tickets/{ticketId}/repliesAdds a reply to an existing Support Ticket.
Path Parameters
The ID of the Support Ticket.
Request Body Schema
The content of your reply.
Request Samples
- Shell
- CLI
curl -H "Content-Type: application/json" \
-H "Authorization: Bearer $TOKEN" \
-X POST -d '{
"description": "Thank you for your help. I was able to figure out what the problem was and I successfully reset my password. You guys are the best!"
}' \
https://api.linode.com/v4/support/tickets/11223344/replies
Response Samples
- 200
- default
{
"created": "2015-06-02T14:31:41",
"id": 1234,
"description": "Hello,\\nI'm sorry to hear that you are having trouble resetting the root password of your Linode. Just to be sure, have you tried to follow the instructions in our online documentation? The link is here:\\n \\nhttps://linode.com/docs/guides/reset-the-root-password-on-your-linode/ \\n\\nIf you have, please reply with any additional steps you have also taken.\\n\\nRegards, Linode Support Team\n",
"created_by": "John Q. Linode",
"gravatar_id": "474a1b7373ae0be4132649e69c36ce30",
"from_linode": true
}Responses
200: Reply created.
The date and time this Ticket reply was created.
The unique ID of this Support Ticket reply.
The body of this Support Ticket reply.
The User who submitted this reply.
The Gravatar ID of the User who created this reply.
If set to true, this reply came from a Linode employee.
default: Error
What happened to cause this error. In most cases, this can be fixed immediately by changing the data you sent in the request, but in some cases you will be instructed to open a Support Ticket or perform some other action before you can complete the request successfully.
The field in the request that caused this error. This may be a path, separated by periods in the case of nested fields. In some cases this may come back as "null" if the error is not specific to any single element of the request.