You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`summary`|`str`| A concise overview of the main functionality of the endpoint. This brief introduction is usually displayed in autogenerated API documentation and helps consumers quickly understand what the endpoint does. |
961
-
|`description`|`str`| A more detailed explanation of the endpoint, which can include information about the operation's behavior, including side effects, error states, and other operational guidelines. |
962
-
|`responses`|`Dict[int, Dict[str, Any]]`| A dictionary that maps each HTTP status code to a Response Object as defined by the [OpenAPI Specification](https://swagger.io/specification/#response-object). This allows you to describe expected responses, including default or error messages, and their corresponding schemas for different status codes. |
963
-
|`response_description`|`str`| Provides the default textual description of the response sent by the endpoint when the operation is successful. It is intended to give a human-readable understanding of the result. |
964
-
|`tags`|`List[str]`| Tags are a way to categorize and group endpoints within the API documentation. They can help organize the operations by resources or other heuristic. |
965
-
|`operation_id`|`str`| A unique identifier for the operation, which can be used for referencing this operation in documentation or code. This ID must be unique across all operations described in the API. |
966
-
|`include_in_schema`|`bool`| A boolean value that determines whether or not this operation should be included in the OpenAPI schema. Setting it to `False` can hide the endpoint from generated documentation and schema exports, which might be useful for private or experimental endpoints. |
|`summary`|`str`| A concise overview of the main functionality of the endpoint. This brief introduction is usually displayed in autogenerated API documentation and helps consumers quickly understand what the endpoint does.|
961
+
|`description`|`str`| A more detailed explanation of the endpoint, which can include information about the operation's behavior, including side effects, error states, and other operational guidelines.|
962
+
|`responses`|`Dict[int, Dict[str, OpenAPIResponse]]`| A dictionary that maps each HTTP status code to a Response Object as defined by the [OpenAPI Specification](https://swagger.io/specification/#response-object). This allows you to describe expected responses, including default or error messages, and their corresponding schemas or models for different status codes. |
963
+
|`response_description`|`str`| Provides the default textual description of the response sent by the endpoint when the operation is successful. It is intended to give a human-readable understanding of the result.|
964
+
|`tags`|`List[str]`| Tags are a way to categorize and group endpoints within the API documentation. They can help organize the operations by resources or other heuristic.|
965
+
|`operation_id`|`str`| A unique identifier for the operation, which can be used for referencing this operation in documentation or code. This ID must be unique across all operations described in the API.|
966
+
|`include_in_schema`|`bool`| A boolean value that determines whether or not this operation should be included in the OpenAPI schema. Setting it to `False` can hide the endpoint from generated documentation and schema exports, which might be useful for private or experimental endpoints.|
967
967
968
968
To implement these customizations, include extra parameters when defining your routes:
0 commit comments