Disable KMS Key

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://openapi-v2.exoscale.com/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "Exoscale APIv2 MCP server": {
    "url": "https://openapi-v2.exoscale.com/mcp"
  }
}
Close
POST /kms-key/{id}/disable

Disables a KMS Key by setting its state to "disabled". This prevents the use of the KMS key for cryptographic and key lifecycle operations.

Path parameters

  • id string(uuid) Required

Responses

  • 200 application/json

    Key disabled

    Hide response attribute Show response attribute object
    • status string Required

      Values are success, target-registered, or already-applied. Default value is success.
  • 400 application/json

    Errors

    Key Not Found: The request was rejected because the specified KMS Key could not be found.

    Key is Pending Deletion: The request was rejected because it was performed on a key that is pending deletion.

    Not on Default: The request was rejected because the operation is not allowed on the default key.

    Hide response attributes Show response attributes object
    • type string(uri-reference) Required

      An absolute or relative URI reference pointing to human-readable documentation concerning the specific problem type encountered.

    • title string Required

      A brief summary defining the class of failure, optimal for quick user interface groupings.

    • status integer Required

      Minimum value is 100, maximum value is 599.

    • detail string Required

      A highly contextual, readable explanation breaking down explicitly what triggered this error scenario.
POST /kms-key/{id}/disable 
curl \
 --request POST 'https://api-ch-gva-2.exoscale.com/v2/kms-key/{id}/disable'
Response examples (200) 
{
  "status": "success"
}
Response examples (400) 
{
  "type": "string",
  "title": "string",
  "status": 42,
  "detail": "string"
}