fix: align Authorization and error response descriptions across all languages

- Update Authorization description to match other API files
- Add bearerFormat field for consistency
- Ensure FileError, FileTooLarge, UnsupportedFileType descriptions are aligned
- Maintain semantic consistency across English, Chinese, and Japanese versions

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
lyzno1
2025-08-14 19:25:23 +08:00
parent bca77f09e9
commit 4023ab62eb
3 changed files with 6 additions and 3 deletions

View File

@@ -1711,7 +1711,8 @@
"ApiKeyAuth": {
"type": "http",
"scheme": "bearer",
"description": "API Key authentication. Provide the key in the 'Authorization' header as 'Bearer {API_KEY}'."
"bearerFormat": "API_KEY",
"description": "API Key authentication. For all API requests, include your API Key in the `Authorization` HTTP Header, prefixed with 'Bearer '. Example: `Authorization: Bearer {API_KEY}`. **Strongly recommend storing your API Key on the server-side, not shared or stored on the client-side, to avoid possible API-Key leakage that can lead to serious consequences.**"
}
},
"responses": {

View File

@@ -1711,7 +1711,8 @@
"ApiKeyAuth": {
"type": "http",
"scheme": "bearer",
"description": "APIキー認証。'Authorization'ヘッダーに'Bearer {API_KEY}'形式でキーを提供してください。"
"bearerFormat": "API_KEY",
"description": "APIキー認証。すべてのAPIリクエストにおいて、Authorization HTTPヘッダーにAPIキーを含めてください。形式Bearer {API_KEY}。**APIキーの漏洩を防ぐため、APIキーはクライアント側で共有または保存せず、サーバー側で保存することを強くお勧めします。**"
}
},
"responses": {

View File

@@ -1711,7 +1711,8 @@
"ApiKeyAuth": {
"type": "http",
"scheme": "bearer",
"description": "API 密钥身份验证。在 'Authorization' 标头中以 'Bearer {API_KEY}' 格式提供密钥。"
"bearerFormat": "API_KEY",
"description": "API-Key 鉴权。所有 API 请求都应在 `Authorization` HTTP Header 中包含您的 API-Key格式为 `Bearer {API_KEY}`。**强烈建议开发者把 API-Key 放在后端存储,而非分享或者放在客户端存储,以免 API-Key 泄露,导致财产损失。**"
}
},
"responses": {