Odata $metadata routing with Azure API Management and adding route in Swagger

Question

I am running into a trouble putting an existing Web API project and creating a OData enabled new end point. Although most of the filters work in local and in APIM the /$metadata seemed to be not working. While hosting the API in .netCore 2.2 in AAM the /$metadata route getting generated related to the Azure hosted Web App and not that of Azure API Management. We thought of adding it to swagger definition explicitly but we were unable to do that too for /$metadata and as such getting 404 resource not found error while trying to access it? The /$metadata endpoint doesn't even follow the controller and action method pattern. It's like `

Blockquote

https://abc.azure.net/$metadata#ddd` or https://abc.azure.net/$metadata

structure.

I can't get over the feeling I've missed something here. Is there a way of defining some sort of wildcard portion to the operation? I can't find anything like that in the AAM documentation. I kept on thinking is there anything I need to do but I am now out of ideas so request if someone can point me in right direction that why the routes generated after deploying to AAM it is of web app normal route rather than AAM API routes?

Did you try manually defining operation in APIM with URL template of "/$metadata"? — Vitaliy Kurokhtin
I created route explicity for swagger as APIM was generating route based on the swagger definition. I was getting error because of API +OData route saying two get operatwith same operation Id — somnath roy

Chun Liu Chun Liu · Accepted Answer · 2020-07-20T03:06:55

The URL template of APIM supports wildcard. Here is a similar which might be helpful for your scenario Azure API Management issue with OData

Odata $metadata routing with Azure API Management and adding route in Swagger

1 Answers