Skip to main content
POST
Request orphan cleanup
Required permissions: server.remove. Personal keys are capped by their owner’s current team role. Supply an Idempotency-Key for this action. An accepted request may continue asynchronously; poll the returned ID. See request conventions and automation workflows. MCP clients use the task-oriented tool catalogue.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Idempotency-Key
string
required
Required string length: 1 - 255

Path Parameters

serverId
string<uuid>
required
Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$

Body

application/json
items
object[]
required
Required array length: 1 - 100 elements

Response

The cleanup operation and whether the request was replayed. Accepted work continues asynchronously; poll its ID. An idempotent replay returns 200.

operation
object
required
replayed
boolean
required
localization
object
required
Last modified on September 5, 2026