OpenAPI schema for addKey/editKey missing several supported fields

[sususu98]

Problem

The OpenAPI schema definitions for addKey and editKey in src/app/api/actions/[...route]/route.ts are missing several fields that the backend Server Actions actually support. This causes these parameters to not appear in the Scalar/Swagger API documentation, even though passing them via the API works correctly.

Missing Fields

editKey (line 291-301)

Missing from requestSchema:

• providerGroup (string | null, optional) - Provider group assignment (admin-only)
• isEnabled (boolean, optional) - Enable/disable key
• dailyResetMode ("fixed" | "rolling", optional) - Daily limit reset mode
• dailyResetTime (string, optional) - Daily reset time (HH:mm format, fixed mode only)
• cacheTtlPreference ("inherit" | "5m" | "1h", optional) - Cache TTL preference

addKey (line 263-274)

Missing from requestSchema:

• providerGroup (string | null, optional) - Provider group assignment
• isEnabled (boolean, optional) - Whether the key is enabled on creation
• dailyResetMode ("fixed" | "rolling", optional) - Daily limit reset mode
• dailyResetTime (string, optional) - Daily reset time (HH:mm format)
• cacheTtlPreference ("inherit" | "5m" | "1h", optional) - Cache TTL preference

Impact

• API consumers relying on Scalar/Swagger docs cannot discover these fields
• providerGroup is particularly important as it controls provider routing for keys, and users may think it can only be set at the user level

Expected Behavior

The OpenAPI requestSchema should include all fields that the corresponding Server Action accepts, so that Scalar/Swagger documentation accurately reflects the full API surface.

[coderabbitai]

🔗 Related PRs

#668 - feat: timezone consistency & rate-limit lease-based quota [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[github-actions]

Thank you for reporting this issue.

Analysis:
I have verified your findings. The OpenAPI schema definitions in src/app/api/actions/[...route]/route.ts are indeed missing several fields that the Server Actions accept.

Missing fields confirmed:

For addKey (route.ts lines 263-274), missing from requestSchema:

• providerGroup (string | null, optional) - accepted at keys.ts line 102
• isEnabled (boolean, optional) - accepted at keys.ts line 92
• dailyResetMode ("fixed" | "rolling", optional) - accepted at keys.ts line 96
• dailyResetTime (string, optional) - accepted at keys.ts line 97
• cacheTtlPreference ("inherit" | "5m" | "1h", optional) - accepted at keys.ts line 103

For editKey (route.ts lines 291-301), missing from requestSchema:

• providerGroup (string | null, optional) - accepted at keys.ts line 345
• isEnabled (boolean, optional) - accepted at keys.ts line 336
• dailyResetMode ("fixed" | "rolling", optional) - accepted at keys.ts line 339
• dailyResetTime (string, optional) - accepted at keys.ts line 340
• cacheTtlPreference ("inherit" | "5m" | "1h", optional) - accepted at keys.ts line 346

Affected code:

• src/app/api/actions/[...route]/route.ts (lines 263-274, 291-301) - OpenAPI schema definitions
• src/actions/keys.ts (lines 88-103, 330-346) - Server Actions that accept the full parameter set

Impact confirmed:
As you noted, API consumers using the Scalar/Swagger documentation at /api/actions/scalar or /api/actions/docs cannot discover these fields, even though passing them via direct API calls works correctly. This is particularly problematic for providerGroup which controls provider routing.

Files to modify:

• src/app/api/actions/[...route]/route.ts - Add the missing fields to both addKey and editKey request schemas

---

Automated response from Claude AI

[SoutikNandy]

I would like to work on this

[github-actions]

This issue has been automatically marked as stale because it has not had any activity in the last 30 days.

If this issue is still relevant:

• Please comment to keep it open
• Add any new information that might help resolve it

This issue will be automatically closed in 14 days if there is no further activity.