Schedule KMS Key Deletion

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}/schedule-deletion

Schedules a KMS key for deletion after a delay. You can specify a delay of 7-30 days.

Path parameters

  • id string(uuid) Required
application/json

Body Required

  • delay-days integer

    Number of days to wait until deletion is final.

    Minimum value is 7, maximum value is 30. Default value is 30.

Responses

  • 200 application/json

    200

    Hide response attribute Show response attribute object
    • delete-at string(date-time)

      Timestamp of the key deletion
  • 400 application/json

    400

    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}/schedule-deletion 
curl \
 --request POST 'https://api-ch-gva-2.exoscale.com/v2/kms-key/{id}/schedule-deletion' \
 --header "Content-Type: application/json" \
 --data '{"delay-days":30}'
Request examples 
{
  "delay-days": 30
}
Response examples (200) 
{
  "delete-at": "2026-05-04T09:42:00Z"
}
Response examples (400) 
{
  "type": "string",
  "title": "string",
  "status": 42,
  "detail": "string"
}