Azure APIM Open API Spec version 3.1.X seems not working

Prashanth Gantela 5

The Azure APIM documentation below says it supports the latest version of Open API Spec 3.1 however, the Spec updated with 3.1 version is not being considered/rendered properly in the page.

Still the 3.0.x version works properly as expected but not 3.1 version. Can anyone help here?

JananiRamesh-MSFT 27,021 Reputation points

2024-08-12T13:11:07.6+00:00

@Prashanth Gantela Thanks for reaching out. could you please share the error message to investigate further?
Prashanth Gantela 5 Reputation points

2024-08-13T14:58:51.6933333+00:00

Thanks @JananiRamesh-MSFT . There is no error but the display problem is with the multipart form data when rendering the OpenAPI Spec

Swagger

From APIM
JananiRamesh-MSFT 27,021 Reputation points

2024-08-15T17:06:40.2966667+00:00

@Prashanth Gantela could you please share me the openAPI file?
Prashanth Gantela 5 Reputation points

2024-08-16T11:07:13.5+00:00

Hi @JananiRamesh-MSFT unable to upload the file here. Tried multiple times as pasting the entire text, attaching .txt/.log file also but still unable to update the comment here. Can you please share your email id to share
JananiRamesh-MSFT 27,021 Reputation points

2024-08-16T13:45:52.3633333+00:00

@Prashanth Gantela Could you please share the openapi file to [email protected] and we'll get back to you promptly:

• Subject: "Attn: Janani "

• Email body: A link to this thread so we can validate and expedite the request

Razvan Mandache 0

The OpenAPI specification for version 3.1.0 added a "summary" field under "info" which doesn't seem to be supported by Azure APIM when importing a json specification file.

{
  "openapi": "3.1.0",
  "info": {
    "title": "My API",
    "version": "1.0",
	"summary": "Summary test"
  },
  ...
}

One or more fields contain incorrect values:
- Parsing error(s): summary is not a valid property at #/info []
- Parsing error(s): The input OpenAPI file is not valid for the OpenAPI specification https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md (schema https://github.com/OAI/OpenAPI-Specification/blob/master/schemas/v3.0/schema.yaml).

1 answer

JananiRamesh-MSFT 27,021 Reputation points

2024-08-23T05:20:15.7066667+00:00

@Prashanth Gantela Thanks for your patience! Currently, while importing Open API, fields such as content -> format, required etc. (may include other fields also) are being ignored when Content-Type is multipart/form-data. This is a known issue that our product team is aware of and working on it (similar discussion). Unfortunately, we don't have a workaround yet let me check internally for an ETA and get back to you.

https://learn.microsoft.com/en-us/answers/questions/1420004/post-request-using-multipart-form-data-and-open-ap

Sorry for the inconvenience caused by this issue.
Please sign in to rate this answer.
Prashanth Gantela 5 Reputation points

2024-08-23T14:26:31.8766667+00:00

ok Thanks @JananiRamesh-MSFT for confirmation.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure APIM Open API Spec version 3.1.X seems not working

1 answer

Your answer