inconsistent-api-naming
Mixed naming conventions (snake_case/camelCase) in API code cause bugs
Applies to: Go, JavaScript, Python, Ruby, Rust, TypeScript
Why this matters
When your frontend uses camelCase (userName) but your backend uses snake_case (user_name), you'll get undefined values and hard-to-debug issues. Pick one convention and stick to it, or use explicit transformations.
Catch it before it ships
pip install stablestack # or: npx stablestackstablestack # scans your project, API002 includedstablestack explain API002API002 is part of the Pro rule set. See pricing — the free tier ships 24 checks with no signup.
False positive in your codebase? Suppress a single line with # noqa: API002
More API Contracts checks
unhandled-api-error
API calls without error handling will crash on network failures
API003missing-content-type
POST/PUT requests without Content-Type may fail or be misinterpreted
API004hardcoded-api-url
Hardcoded API URLs make it hard to switch between environments
API005api-type-alignment
Backend endpoints should have response_model; frontend should use generated types.
API006cross-file-type-mismatch
Cross-file type mismatch between API endpoint and client call site.
API007untyped-api-response
API endpoint has no typed response — consumers can't rely on the response shape.