api-contract-enforcement

Run the validation script with your OpenAPI YAML or JSON file and the Python module containing your FastAPI app as arguments. The script extracts routes from the app automatically and compares them against every path, method, and schema in the spec.

Execute the validation script as a pipeline step before deployment. It exits with code 0 when the implementation matches the spec and code 1 on violations, so the pipeline fails automatically on contract mismatches.

Yes, the validator supports Flask by inspecting the app's URL map for routes and methods. However, Flask lacks automatic schema extraction, so request body and response validation is limited compared to FastAPI's Pydantic-based introspection.

This occurs when the parameter name in the spec differs from the implementation, such as '{id}' in the spec versus '{user_id}' in the route. Rename the parameter in either the spec or the route handler so both match exactly.

Standard mode reports critical violations like missing endpoints and mismatched path parameters. Strict mode additionally fails on warnings such as type mismatches, extra response fields, and missing validation constraints, suiting production deployment gates.