package openapi.v3

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message AdditionalPropertiesItem

OpenAPIv3.proto:47

Used in: Schema

message Any

OpenAPIv3.proto:54

Used in: AnyOrExpression, Example, Header, MediaType, NamedAny, Parameter, Schema

message AnyOrExpression

OpenAPIv3.proto:59

Used in: Link

message Callback

OpenAPIv3.proto:67

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: CallbackOrReference

message CallbackOrReference

OpenAPIv3.proto:72

Used in: NamedCallbackOrReference

message CallbacksOrReferences

OpenAPIv3.proto:79

Used in: Components, Operation

message Components

OpenAPIv3.proto:84

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: Document

message Contact

OpenAPIv3.proto:98

Contact information for the exposed API.

Used in: Info

message DefaultType

OpenAPIv3.proto:105

Used in: Schema

message Discriminator

OpenAPIv3.proto:114

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: Schema

message Document

OpenAPIv3.proto:120

message Encoding

OpenAPIv3.proto:133

A single encoding definition applied to a single schema property.

Used in: NamedEncoding

message Encodings

OpenAPIv3.proto:142

Used in: MediaType

message Example

OpenAPIv3.proto:146

Used in: ExampleOrReference

message ExampleOrReference

OpenAPIv3.proto:154

Used in: NamedExampleOrReference

message ExamplesOrReferences

OpenAPIv3.proto:161

Used in: Components, Header, MediaType, Parameter

message Expression

OpenAPIv3.proto:165

Used in: AnyOrExpression

message ExternalDocs

OpenAPIv3.proto:170

Allows referencing an external resource for extended documentation.

Used in: Document, Operation, Schema, Tag

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: HeaderOrReference

message HeaderOrReference

OpenAPIv3.proto:192

Used in: NamedHeaderOrReference

message HeadersOrReferences

OpenAPIv3.proto:199

Used in: Components, Encoding, Response

message Info

OpenAPIv3.proto:204

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: Document

message ItemsItem

OpenAPIv3.proto:215

Used in: Schema

message License

OpenAPIv3.proto:220

License information for the exposed API.

Used in: Info

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: LinkOrReference

message LinkOrReference

OpenAPIv3.proto:237

Used in: NamedLinkOrReference

message LinksOrReferences

OpenAPIv3.proto:244

Used in: Components, Response

message MediaType

OpenAPIv3.proto:249

Each Media Type Object provides schema and examples for the media type identified by its key.

Used in: NamedMediaType

message MediaTypes

OpenAPIv3.proto:257

Used in: Header, Parameter, RequestBody, Response

message NamedAny

OpenAPIv3.proto:262

Automatically-generated message used to represent maps of Any as ordered (name,value) pairs.

Used in: Callback, Components, Contact, Discriminator, Document, Encoding, Example, Expression, ExternalDocs, Header, Info, License, Link, MediaType, OauthFlow, OauthFlows, Object, Operation, Parameter, PathItem, Paths, RequestBody, Response, Responses, Schema, SecurityScheme, Server, ServerVariable, Tag, Xml

message NamedCallbackOrReference

OpenAPIv3.proto:270

Automatically-generated message used to represent maps of CallbackOrReference as ordered (name,value) pairs.

Used in: CallbacksOrReferences

message NamedEncoding

OpenAPIv3.proto:278

Automatically-generated message used to represent maps of Encoding as ordered (name,value) pairs.

Used in: Encodings

message NamedExampleOrReference

OpenAPIv3.proto:286

Automatically-generated message used to represent maps of ExampleOrReference as ordered (name,value) pairs.

Used in: ExamplesOrReferences

message NamedHeaderOrReference

OpenAPIv3.proto:294

Automatically-generated message used to represent maps of HeaderOrReference as ordered (name,value) pairs.

Used in: HeadersOrReferences

message NamedLinkOrReference

OpenAPIv3.proto:302

Automatically-generated message used to represent maps of LinkOrReference as ordered (name,value) pairs.

Used in: LinksOrReferences

message NamedMediaType

OpenAPIv3.proto:310

Automatically-generated message used to represent maps of MediaType as ordered (name,value) pairs.

Used in: MediaTypes

message NamedParameterOrReference

OpenAPIv3.proto:318

Automatically-generated message used to represent maps of ParameterOrReference as ordered (name,value) pairs.

Used in: ParametersOrReferences

message NamedPathItem

OpenAPIv3.proto:326

Automatically-generated message used to represent maps of PathItem as ordered (name,value) pairs.

Used in: Callback, Paths

message NamedRequestBodyOrReference

OpenAPIv3.proto:334

Automatically-generated message used to represent maps of RequestBodyOrReference as ordered (name,value) pairs.

Used in: RequestBodiesOrReferences

message NamedResponseOrReference

OpenAPIv3.proto:342

Automatically-generated message used to represent maps of ResponseOrReference as ordered (name,value) pairs.

Used in: Responses, ResponsesOrReferences

message NamedSchemaOrReference

OpenAPIv3.proto:350

Automatically-generated message used to represent maps of SchemaOrReference as ordered (name,value) pairs.

Used in: Properties, SchemasOrReferences

message NamedSecuritySchemeOrReference

OpenAPIv3.proto:358

Automatically-generated message used to represent maps of SecuritySchemeOrReference as ordered (name,value) pairs.

Used in: SecuritySchemesOrReferences

message NamedServerVariable

OpenAPIv3.proto:366

Automatically-generated message used to represent maps of ServerVariable as ordered (name,value) pairs.

Used in: ServerVariables

message NamedString

OpenAPIv3.proto:374

Automatically-generated message used to represent maps of string as ordered (name,value) pairs.

Used in: Strings

message NamedStringArray

OpenAPIv3.proto:382

Automatically-generated message used to represent maps of StringArray as ordered (name,value) pairs.

Used in: SecurityRequirement

message OauthFlow

OpenAPIv3.proto:390

Configuration details for a supported OAuth Flow

Used in: OauthFlows

message OauthFlows

OpenAPIv3.proto:399

Allows configuration of the supported OAuth Flows.

Used in: SecurityScheme

message Object

OpenAPIv3.proto:407

message Operation

OpenAPIv3.proto:412

Describes a single API operation on a path.

Used in: PathItem

message Parameter

OpenAPIv3.proto:429

Describes a single operation parameter. A unique parameter is defined by a combination of a name and location.

Used in: ParameterOrReference

message ParameterOrReference

OpenAPIv3.proto:446

Used in: NamedParameterOrReference, Operation, PathItem

message ParametersOrReferences

OpenAPIv3.proto:453

Used in: Components

message PathItem

OpenAPIv3.proto:458

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: NamedPathItem

message Paths

OpenAPIv3.proto:476

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: Document

message Properties

OpenAPIv3.proto:481

Used in: Schema

message Reference

OpenAPIv3.proto:486

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: CallbackOrReference, ExampleOrReference, HeaderOrReference, LinkOrReference, ParameterOrReference, RequestBodyOrReference, ResponseOrReference, SchemaOrReference, SecuritySchemeOrReference

message RequestBodiesOrReferences

OpenAPIv3.proto:492

Used in: Components

message RequestBody

OpenAPIv3.proto:497

Describes a single request body.

Used in: RequestBodyOrReference

message RequestBodyOrReference

OpenAPIv3.proto:504

Used in: NamedRequestBodyOrReference, Operation

message Response

OpenAPIv3.proto:512

Describes a single response from an API Operation, including design-time, static `links` to operations based on the response.

Used in: ResponseOrReference

message ResponseOrReference

OpenAPIv3.proto:520

Used in: NamedResponseOrReference, Responses

message Responses

OpenAPIv3.proto:528

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: Operation

message ResponsesOrReferences

OpenAPIv3.proto:534

Used in: Components

message Schema

OpenAPIv3.proto:539

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: SchemaOrReference

message SchemaOrReference

OpenAPIv3.proto:578

Used in: AdditionalPropertiesItem, Header, ItemsItem, MediaType, NamedSchemaOrReference, Parameter, Schema

message SchemasOrReferences

OpenAPIv3.proto:585

Used in: Components

message SecurityRequirement

OpenAPIv3.proto:590

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: Document, Operation

message SecurityScheme

OpenAPIv3.proto:595

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: SecuritySchemeOrReference

message SecuritySchemeOrReference

OpenAPIv3.proto:607

Used in: NamedSecuritySchemeOrReference

message SecuritySchemesOrReferences

OpenAPIv3.proto:614

Used in: Components

message Server

OpenAPIv3.proto:619

An object representing a Server.

Used in: Document, Link, Operation, PathItem

message ServerVariable

OpenAPIv3.proto:627

An object representing a Server Variable for server URL template substitution.

Used in: NamedServerVariable

message ServerVariables

OpenAPIv3.proto:634

Used in: Server

message SpecificationExtension

OpenAPIv3.proto:639

Any property starting with x- is valid.

message StringArray

OpenAPIv3.proto:647

Used in: NamedStringArray

message Strings

OpenAPIv3.proto:651

Used in: Discriminator, OauthFlow

message Tag

OpenAPIv3.proto:656

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: Document

message Xml

OpenAPIv3.proto:664

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: Schema