From fb45c3259385dfc5a58e08ddc8f5d673fcf42d67 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 14 Oct 2026 11:28:28 +0000 Subject: [PATCH] docs: fix openapi response for DELETE /admin/users/{userId} The spec documented a 200 response returning UserSchema, but the adminUserDelete handler always returns an empty JSON object for hard delete, soft delete, and already soft-deleted users. Document the empty object response and the optional should_soft_delete request body. Co-Authored-By: Claude Sonnet 5.5 Claude-Session: https://claude.ai/code/session_0137vz1dKsd2RZigEqmeo8N3 --- openapi.yaml | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/openapi.yaml b/openapi.yaml index 1f04ee575d..41c20d1dde 100644 --- a/openapi.yaml +++ b/openapi.yaml @@ -1959,13 +1959,25 @@ paths: security: - APIKeyAuth: [] AdminAuth: [] + requestBody: + content: + application/json: + schema: + type: object + properties: + should_soft_delete: + type: boolean + default: false + description: Soft delete the user instead of permanently deleting their account. responses: 200: - description: User's account data. + description: Empty JSON object. No user data is returned after hard or soft deletion. content: application/json: schema: - $ref: "#/components/schemas/UserSchema" + type: object + additionalProperties: false + example: {} 401: $ref: "#/components/responses/UnauthorizedResponse" 403: