API: Reboot Server

This method provides a way to reboot the server for a specific (mt) Media Temple service that is associated with the authenticated account.

IMPORTANT: As of April 2018, the Media Temple customer API has been deprecated. Previously created API keys will continue to work until further notice, but you will not be able to generate new keys via the Account Center. If you have any questions about this, please feel free to contact our support team.

Request Info

The following URL and HTTP method should be used.


The following parameters must be provided in the URL.

Parameter Type Description
serviceId int The service id

Response Info

The response will return an HTTP status code to indicate the general category of success or failure to the client. More specific error codes and messages will be contained in the response data itself, if provided. For more information on response codes and parsing response data, see Parsing API Responses.

Sample Request

To get a list of services in JSON format, do the following.

curl -D log.txt -s -X "POST" ""

Sample Response

Here is an example of the returned result.

"response" : {
"statusCode" : 202,
"timeStamp" : 1284609174311,
"date" : "2010-09-16T03:52:54.311+0000",
"errors" : [ ],
"custom" : [ ]

Sample Operation Pending

If another set reboot operation is already pending (e.g. the above request is called a second time before the reboot job has completed), then you can expect a response like the following.

"response" : {
"statusCode" : 409,
"timeStamp" : 1284609198593,
"date" : "2010-09-16T03:53:18.593+0000",
"errors" : [ {
"errorCode" : "OperationPending",
"message" : "An existing operation that conflicts is currently pending.  This operation cannot be scheduled until it completes."
} ],
"custom" : [ ]

Response Fields

All responses should be in the standard response format. For more information, see Parsing API Responses.

Response Errors

Status Code Error Code Error Description
404 InvalidService The specified serviceId was invalid.
409 OperationPending There is an existing operation that has not completed.
500 UnknownError There was an unexpected error.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk