Operation
- class Operation(d: dict[str, Any] = None, tags: list[str] = None, summary: str = None, description: str = None, externalDocs: ExternalDocumentation = None, operationId: str = None, parameters: list[Parameter | Reference] = None, requestBody: RequestBody | Reference = None, responses: Responses = None, callbacks: dict[str, Callback | Reference] = None, deprecated: bool = None, security: list[SecurityRequirement] = None, servers: list[Server] = None)
Describes a single API operation on a path.
- property tags: list[str] | None
A list of tags for API documentation control. Tags can be used for logical grouping of operations by resources or any other qualifier.
- property summary: str | None
A short summary of what the operation does
- property description: str | None
A verbose explanation of the operation behavior. CommonMark syntax MAY be used for rich text representation.
- property externalDocs: ExternalDocumentation | None
Additional external documentation for this operation.
- property operationId: str | None
Unique string used to identify the operation. The id MUST be unique among all operations described in the API. The operationId value is case-sensitive. Tools and libraries MAY use the operationId to uniquely identify an operation, therefore, it is RECOMMENDED to follow common programming naming conventions.
- property parameters: list[Parameter | Reference] | None
A list of parameters that are applicable for this operation. If a parameter is already defined at the Path Item, the new definition will override it but can never remove it. The list MUST NOT include duplicated parameters. A unique parameter is defined by a combination of a name and location. The list can use the Reference Object to link to parameters that are defined in the OpenAPI Object’s components.parameters.
- property requestBody: RequestBody | Reference | None
The request body applicable for this operation. The requestBody is fully supported in HTTP methods where the HTTP 1.1 specification RFC7231 has explicitly defined semantics for request bodies. In other cases where the HTTP spec is vague (such as GET, HEAD and DELETE), requestBody is permitted but does not have well-defined semantics and SHOULD be avoided if possible.
- property responses: Responses | None
The list of possible responses as they are returned from executing this operation.
- property callbacks: dict[str, Callback | Reference] | None
A map of possible out-of band callbacks related to the parent operation. The key is a unique identifier for the Callback Object. Each value in the map is a Callback Object that describes a request that may be initiated by the API provider and the expected responses.
- property deprecated: bool | None
Declares this operation to be deprecated. Consumers SHOULD refrain from usage of the declared operation. Default value is false.
- property security: list[SecurityRequirement] | None
A declaration of which security mechanisms can be used for this operation. The list of values includes alternative Security Requirement Objects that can be used. Only one of the Security Requirement Objects need to be satisfied to authorize a request. To make security optional, an empty security requirement ({}) can be included in the array. This definition overrides any declared top-level security. To remove a top-level security declaration, an empty array can be used.