How can we improve Azure API Management?

Support in "produces" section the Accept-Header from OpenAPI specification

The produces/consumes is MIME type.
1. The “consumes” specify the format that the API can accept. So “consumes” only affects operations with a request body, such as POST, PUT and PATCH.
And is sent via “Content-Type” header
2. The “produces” specify the format that the API can return.
And I sent via “Accept” header

Using the “Accept” header the user can select needed API response MIME type (e.g. "text/plain", "application/octet-stream", "*/*").

When sending a request with SwaggerUI, We can selecte "application/octet-stream" Response Content Type.
The request was sent by Swagger UI with the “Accept” header value filled "application/octet-stream".

In the APIM Developer Portal We are not able to select Response Content Type "application/octet-stream". It's just ignore "produces" section.

So from my opinion the “Produces” section should be presented in the Developer Portal in from of “Accept” header field.
Just like it’s done for “Consumes” section, which is presented as “Content-Type” header.

51 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Aliaksandr Trafimenka shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base