Even OpenAPI contracts that are structurally correct may have issues with the semantics of the fields in them. For example, the API could include invalid email and URL formats, or inconsistent property formats across the API definition.
This section provides details of the possible semantic issues in your API and to fix how them.
- 'BasePath' property does not match the pattern constraining 'basePath' values'Host' property does not match the pattern constraining host values'OperationId' is not unique throughout the OpenAPI definition'Url' or 'email' property does not match the pattern constraining url or email valuesDefault value for the array item is not consistent with the item's typeDefault value for the header is not consistent with the header's typeDefault value for the parameter is not consistent with the parameter's typeDefault value for the schema property is not consistent with the property's typeEnum value for the header is not consistent with the header's typeEnum value for the items of an array is not consistent with the items typeEnum value for the parameter is not consistent with the parameter's typeEnum value for the schema is not consistent with the schema's typeExample is not consistent with 'mediaType' defined in the operation's 'produces' propertyFile parameter is used in an operation where the 'consumes' property does not allow itHeader parameters have the same nameHTTP status codes in responses must be between 100 and 599Operation defines both a body parameter and a 'formData' parameterOperation defines multiple body parametersParameters have the same name + in combinationPath parameter in the path has no corresponding path templatePath template for the path is emptyPath template has no corresponding path parameter definitionPaths are equivalentProperty 'allowEmptyValue' is only allowed for query parametersProperty is not defined in the OpenAPI SpecificationRequired property is missingSchema discriminator property must be a stringSchema discriminator property must match a property with the same nameSchema does not define a required propertySchema property is not unique throughout 'properties', 'allOf', and 'additionalProperties' fieldsSecurity field of the operation references a security scheme not defined in '#/securityDefinitions'Security field references a security scheme not defined in '#/securityDefinitions'Security requirement is not an OAuth2 requirement and must not define OAuth2 scopesValue of the schema discriminator must be a required property
Copyright 42Crunch 2021