skip to content »

Dating 2 0

dating 2 0-76

The referenced structure MUST be in the format of a Path Item Object.If there are conflicts between the referenced definition and this Path Item's definition, the behavior is Unique string used to identify the operation.

Additional utilities can also take advantage of the resulting files, such as testing tools.The id MUST be unique among all operations described in the API.Tools and libraries MAY use the operation Id to uniquely identify an operation, therefore, it is recommended to follow common programming naming conventions.The container maps a HTTP response code to the expected response.It is not expected from the documentation to necessarily cover all possible HTTP response codes, since they may not be known in advance. If this field does not exist, it means no content is returned as part of the response.The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

The Swagger specification is licensed under The Apache License, Version 2.0.

However, it is expected from the documentation to cover a successful operation response and any known errors. As an extension to the Schema Object, its root Declares the value of the header that the server will use if none is provided.

(Note: "default" has no meaning for required headers.) See https://org/html/draft-fge-json-schema-validation-00#section-6.2.

YAML, being a superset of JSON, can be used as well to represent a Swagger specification file.

For example, if a field is said to have an array value, the JSON array representation will be used: While the API is described using JSON it does not impose a JSON input/output to the API itself.

The Swagger representation of the API is made of a single file.