Review a REST API design
Reviews an endpoint or OpenAPI snippet for naming, status codes, error shape, pagination, idempotency and compatibility, ranked by impact.
此資源僅提供英文版本。
提示詞是你複製到自己助理中的文字。KitLocal 不會執行它們。
填寫變數
你輸入的內容只保留在此瀏覽器中,不會加入 URL、儲存或傳送到任何地方。
預覽
仍需填寫:Endpoints or OpenAPI fragment
Review this HTTP API design. Consumers: . Breaking changes allowed: No.
Check: resource naming, method semantics, status codes, one consistent error shape,
pagination and filtering, idempotency of unsafe retries, authentication and authorization
per endpoint, and backward compatibility. Rank findings as Blocker / Should fix / Nice to have,
each with the exact endpoint, why it matters and a concrete alternative.
Say clearly what you could not judge from the text provided.
Design:
{{spec}}
用途
Catch contract problems before clients depend on them.
適用時機
- You are about to publish or change an HTTP API.
需要準備的內容
- An OpenAPI fragment or a list of endpoints with sample requests and responses.
預期輸出
Findings grouped by Blocker, Should fix and Nice to have.
關於此目錄
內建快照 · 發布於 2026年11月15日 清晨6:05 · 目錄修訂版 5bc079fe355af2214bc0
正在顯示應用程式內建的快照(尚未設定內容來源)。來源處可能已有更新的內容。