Looking through the OpenAPI Spec (previously known as the Swagger file) it doesn't look like it defines connected endpoints. Which makes sense, since it's purpose is to define an interface to an API, not it's underlying implementation. It does, however, provide a way to link to external documentation using the External Documentation Object. This could link to documentation about what endpoints the given API uses.
If you want to get a real-time look at what endpoints your services are consuming take a look at New Relics - Service Map and Instana - Dependency Maps. I'm sure other APM tools do this too, but these are the two I know of. The downfall to these is they are not free.
One other way to do this is write a tool to parse your config files looking for all external dependencies. This, of course, would require standards and naming conventions in your services for identifying those endpoints.