'Can I reuse paths between OpenApi service specifications?

I'm documenting a set of services with open-api 3.0.3. Each shares a set of common endpoint paths. Is there a way to define a path and reuse in multiple specifications? This would be functionally equivalent to the other components sections.

swaggeropenapi


Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source

Related Questions

Is it possible to render Swagger UI from swagger YAML file in ReadeMe.md file ? just to display UI once Commit code in github

How to overcome "Conflicting setter definitions for property "?

Separate swagger implementation from controller code

why I see this when compiling my project in bootstrap? "Found 0 JPA repository interfaces."

Falcon - how to validate incoming requests against Swagger specification?

Swashbuckle - Add Model and Example values to Swagger UI from a Model from another project

Displaying of FastAPI validation errors to end users

How to validate openapi 3.0.0 yaml spec?

Is there a way to define an integer property as int64 in a Joi model that is used by Hapi Swagger

Rails: make authentication to swagger API via devise or other

Enabling authentication in swagger

How to generate java client code for swagger REST API documentation

Spring , How to have Swagger UI send a request without Hypertext Transfer Protocol

Is there a way change the Controller's name in the swagger-ui page?

Code generation to initialise by default to empty list instead of null