Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Used in: , , , , , ,
Used in:
A map of possible out-of band callbacks related to the parent operation. Each value in the map is a Path Item Object that describes a set of requests that may be initiated by the API provider and the expected responses. The key value used to identify the callback object is an expression, evaluated at runtime, that identifies a URL to use for the callback operation.
Used in:
Used in:
Used in: ,
Holds a set of reusable objects for different aspects of the OAS. All objects defined within the components object will have no effect on the API unless they are explicitly referenced from properties outside the components object.
Used in:
Contact information for the exposed API.
Used in:
Used in:
When request bodies or response payloads may be one of a number of different schemas, a `discriminator` object can be used to aid in serialization, deserialization, and validation. The discriminator is a specific object in a schema which is used to inform the consumer of the specification of an alternative schema based on the value associated with it. When using the discriminator, _inline_ schemas will not be considered.
Used in:
A single encoding definition applied to a single schema property.
Used in:
Used in:
Used in:
Used in:
Used in: , , ,
Used in:
Allows referencing an external resource for extended documentation.
Used in: , , ,
The Header Object follows the structure of the Parameter Object with the following changes: 1. `name` MUST NOT be specified, it is given in the corresponding `headers` map. 1. `in` MUST NOT be specified, it is implicitly in `header`. 1. All traits that are affected by the location MUST be applicable to a location of `header` (for example, `style`).
Used in:
Used in:
Used in: , ,
The object provides metadata about the API. The metadata MAY be used by the clients if needed, and MAY be presented in editing or documentation generation tools for convenience.
Used in:
Used in:
License information for the exposed API.
Used in:
The `Link object` represents a possible design-time link for a response. The presence of a link does not guarantee the caller's ability to successfully invoke it, rather it provides a known relationship and traversal mechanism between responses and other operations. Unlike _dynamic_ links (i.e. links provided **in** the response payload), the OAS linking mechanism does not require link information in the runtime response. For computing links, and providing instructions to execute them, a runtime expression is used for accessing values in an operation and using them as parameters while invoking the linked operation.
Used in:
Used in:
Used in: ,
Each Media Type Object provides schema and examples for the media type identified by its key.
Used in:
Used in: , , ,
Automatically-generated message used to represent maps of Any as ordered (name,value) pairs.
Used in: , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Map key
Mapped value
Automatically-generated message used to represent maps of CallbackOrReference as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of Encoding as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of ExampleOrReference as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of HeaderOrReference as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of LinkOrReference as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of MediaType as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of ParameterOrReference as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of PathItem as ordered (name,value) pairs.
Used in: ,
Map key
Mapped value
Automatically-generated message used to represent maps of RequestBodyOrReference as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of ResponseOrReference as ordered (name,value) pairs.
Used in: ,
Map key
Mapped value
Automatically-generated message used to represent maps of SchemaOrReference as ordered (name,value) pairs.
Used in: ,
Map key
Mapped value
Automatically-generated message used to represent maps of SecuritySchemeOrReference as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of ServerVariable as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of string as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Automatically-generated message used to represent maps of StringArray as ordered (name,value) pairs.
Used in:
Map key
Mapped value
Configuration details for a supported OAuth Flow
Used in:
Allows configuration of the supported OAuth Flows.
Used in:
Describes a single API operation on a path.
Used in:
Describes a single operation parameter. A unique parameter is defined by a combination of a name and location.
Used in:
Used in: , ,
Used in:
Describes the operations available on a single path. A Path Item MAY be empty, due to ACL constraints. The path itself is still exposed to the documentation viewer but they will not know which operations and parameters are available.
Used in:
Holds the relative paths to the individual endpoints and their operations. The path is appended to the URL from the `Server Object` in order to construct the full URL. The Paths MAY be empty, due to ACL constraints.
Used in:
Used in:
A simple object to allow referencing other components in the specification, internally and externally. The Reference Object is defined by JSON Reference and follows the same structure, behavior and rules. For this specification, reference resolution is accomplished as defined by the JSON Reference specification and not by the JSON Schema specification.
Used in: , , , , , , , ,
Used in:
Describes a single request body.
Used in:
Used in: ,
Describes a single response from an API Operation, including design-time, static `links` to operations based on the response.
Used in:
Used in: ,
A container for the expected responses of an operation. The container maps a HTTP response code to the expected response. The documentation is not necessarily expected to cover all possible HTTP response codes because they may not be known in advance. However, documentation is expected to cover a successful operation response and any known errors. The `default` MAY be used as a default response object for all HTTP codes that are not covered individually by the specification. The `Responses Object` MUST contain at least one response code, and it SHOULD be the response for a successful operation call.
Used in:
Used in:
The Schema Object allows the definition of input and output data types. These types can be objects, but also primitives and arrays. This object is an extended subset of the JSON Schema Specification Wright Draft 00. For more information about the properties, see JSON Schema Core and JSON Schema Validation. Unless stated otherwise, the property definitions follow the JSON Schema.
Used in:
Used in: , , , , , ,
Used in:
Lists the required security schemes to execute this operation. The name used for each property MUST correspond to a security scheme declared in the Security Schemes under the Components Object. Security Requirement Objects that contain multiple schemes require that all schemes MUST be satisfied for a request to be authorized. This enables support for scenarios where multiple query parameters or HTTP headers are required to convey security information. When a list of Security Requirement Objects is defined on the OpenAPI Object or Operation Object, only one of the Security Requirement Objects in the list needs to be satisfied to authorize the request.
Used in: ,
Defines a security scheme that can be used by the operations. Supported schemes are HTTP authentication, an API key (either as a header, a cookie parameter or as a query parameter), mutual TLS (use of a client certificate), OAuth2's common flows (implicit, password, application and access code) as defined in RFC6749, and OpenID Connect. Please note that currently (2019) the implicit flow is about to be deprecated OAuth 2.0 Security Best Current Practice. Recommended for most use case is Authorization Code Grant flow with PKCE.
Used in:
Used in:
Used in:
An object representing a Server.
Used in: , , ,
An object representing a Server Variable for server URL template substitution.
Used in:
Used in:
Any property starting with x- is valid.
Used in:
Used in: ,
Adds metadata to a single tag that is used by the Operation Object. It is not mandatory to have a Tag Object per tag defined in the Operation Object instances.
Used in:
A metadata object that allows for more fine-tuned XML model definitions. When using arrays, XML element names are *not* inferred (for singular/plural forms) and the `name` property SHOULD be used to add that information. See examples for expected behavior.
Used in: