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.
- 'OperationId' is not unique throughout the OpenAPI definition'OperationId' of the link object does not point to an operation objectDefault value for the schema property is not consistent with the property's typeEnum value for the schema is not consistent with the schema's typeHeader parameters have the same nameHTTP status codes in responses must be between 100 and 599Key used in the encoding map of the schema is not defined in the properties of the schemaLink object has both 'operationId' and 'operationRef' definedMedia type object with 'multipart/form-data' has no schema definedParameters 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 'allowReserved' 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 requirement is not an OAuth2 or OpenID Connect requirement and must not define scopesServer object variable is not used in any server URLsServer object variable used in the server URL is not defined in the server object variablesServer URL must be an absolute URLUploading multiple files is only available for 'multipart/*' media typeValue of the schema discriminator must be a required property
Copyright 42Crunch 2021