Route overloading issues in Azure

Question

I have 2 endpoints implemented in Visual Studio with routes defined respectively like "Part1/Part2/Part3/{ItemAsInteger}" (type of integer) and "Part1/Part2/Part3/{ItemAsString}" (type of string). NSwag for OAS 3.0 generates the JSON for the two endpoints with no issue ( it generates the two separately with the correct type used). However when this JSON was imported into Azure mgmt It complained that these were duplicates.

On way to solve this would be by explicitly disambiguating like "Part1/Part2/Part3/ByString/{ItemAsString}". But we prefer not to do it this way. Is there a way to make Azure import this correctly?

Answer 1

@Dennis Worthem Apology for the delay. This is the the import APIM restrictions as mentioned here. You cannot have the same path for the different endpoint/API. The individual API path should have the unique names while importing to APIM.

Required parameters across both path and query must have unique names. (In OpenAPI a parameter name only needs to be unique within a location, for example path, query, header. However, in API Management we allow operations to be discriminated by both path and query parameters (which OpenAPI doesn't support). That's why we require parameter names to be unique within the entire URL template.)