/api/actions/keys/editKey这个接口报错

[qpdy]

在api/actions/scalar#tag/密钥管理/POST/api/actions/keys/editKey页面，传参数
{
"keyId": 12,
"name": "128"
}，响应状态码400，{
"ok": false,
"error": "Failed query: select "id", "user_id", "key", "name", "is_enabled", "expires_at", "can_login_web_ui", "limit_5h_usd", "limit_daily_usd", "daily_reset_mode", "daily_reset_time", "limit_weekly_usd", "limit_monthly_usd", "limit_total_usd", "limit_concurrent_sessions", "provider_group", "cache_ttl_preference", "created_at", "updated_at", "deleted_at" from "keys" where ("keys"."id" = $1 and "keys"."deleted_at" is null)\nparams: [object Object]"
}这是什么原因？

[github-actions]

Thank you for reporting this issue.

Analysis:

This is a confirmed bug in the API adapter layer. The error occurs because of a parameter passing mismatch between the API route and the underlying editKey action function.

Root Cause:

1. The editKey function in src/actions/keys.ts:204-221 expects two separate arguments:

   export async function editKey(
     keyId: number,
     data: { name: string; ... }
   ): Promise<ActionResult>

2. However, the API adapter in src/lib/api/action-adapter-openapi.ts:246-264 passes the entire request body as a single object when there are multiple parameters:

   // When multiple keys exist in the schema, it passes the whole body
   args = [body];  // Results in: editKey({ keyId: 12, name: "128" })

3. This causes editKey to receive { keyId: 12, name: "128" } as the first argument (keyId), instead of 12.

4. When findKeyById(keyId) is called at src/actions/keys.ts:229, it passes an object { keyId: 12, name: "128" } instead of the number 12, causing the database query to fail with params: [object Object].

Affected code:

• src/lib/api/action-adapter-openapi.ts (lines 246-264) - parameter mapping logic
• src/app/api/actions/[...route]/route.ts (lines 231-252) - editKey route definition

Workaround:

Until this is fixed, you can use the web UI to edit keys, or call the editKey action directly from frontend code rather than through the REST API endpoint.

---

Automated response from Claude AI

[github-actions]

This issue appears to be a duplicate of #230.

Why this is a duplicate:
Both issues report the same root cause - the OpenAPI action adapter passes request body parameters as [object Object] instead of extracting individual primitive values:

• Bug: API接口获取统计数据失败 #230: Invalid time range: [object Object] in getUserStatistics
• /api/actions/keys/editKey这个接口报错 #311: params: [object Object] in editKey SQL query

The underlying bug is in action-adapter-openapi.ts where createActionRoute passes the entire request body object to Server Actions instead of extracting parameters based on the schema.

Original issue: #230
Please follow the discussion there for updates. A fix was attempted in PR #232 but users reported it still persists in v0.3.19.

If you believe this is NOT a duplicate, please explain the difference and we will reopen this issue.

---

Automated duplicate detection by Claude AI