Specification Conformance
You can check for API specification conformance using a custom or MuleSoft-provided ruleset such as:
-
Anypoint Best Practices
-
Authentication Security Best Practices
-
OpenAPI Best Practices
-
AsyncAPI Best Practices
-
Required Examples
See Finding and Fixing Conformance Issues for an overview of ways to validate conformance and determine why conformance failed.
Validate API Specifications Against Rulesets
You can validate specifications against rulesets within the context of your API project regardless of whether your API is centrally governed through Anypoint API Governance. Developers or implementors typically do this either to proactively identify conformance issues or to review issues they’re notified about.
For detailed information about validating specifications against rulesets, see:
-
Anypoint Code Builder: Validating API Specifications Against Governance Rulesets
-
Design Center: Ruleset Dependencies
-
Anypoint CLI: governance:api:validate
Fix Conformance Issues
After you identify conformance issues in your specification, you can fix the issues using your IDE and publish the new version of the specification to Exchange.
For detailed information about fixing API conformance issues, see:
-
Anypoint Code Builder: Fix Conformance Issues
-
Design Center: Ruleset Dependencies in the Design Center documentation