Postman does not handle multiple content types headers from open api specs

[harshpat]

Swagger open api specs has multiple ContentType for same URL.
Should postman duplicate URLs per content-types, instead of just showing one content-type in headers which is at top ?

[abhijitkane]

@harshpat I'd agree using the first one isn't ideal. What's the use-case of different types of request payloads for different content-types? How different would the different schemas be?

We could use JSON>XML>Text as the priority order while determining what request body to use for the main request.

We use Postman's examples to define the various responses that this endpoint can generate. If the assumption is that content type C1 in the request results in content type C1 in the response, we can generate the correct example requests as well.

[jpoehnelt]

There is also the case where there are multiple examples for a specific content type. Current behavior grabs the first example, bar.

content:
    "application/json":
      examples:
        bar: 
          value:
            $ref: ./examples/bar.json
        foo: 
          value:
            $ref: ./examples/foo.json