title: Azure API Management: Discriminate operations by both path and query parameters
body: <p>I have a backend API (that implements <a href="https://docs.microsoft.com/en-us/dotnet/api/system.web.http.apicontroller?view=aspnetcore-2.2" rel="nofollow noreferrer">ApiController</a>) which I'd like to put behind an APIM API. ApiController allows us to discriminate between two different GET operations based on the query parameters that are passed in. When I attempt to define these endpoints in APIM, I get the following error:</p>
  
  <p><a href="https://i.stack.imgur.com/ojDou.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ojDou.png" alt="enter image description here"></a></p>
  
  <p>The message suggests an endpoint is defined solely by the path and operation. But that seems to contradict documentation I found <a href="https://docs.microsoft.com/en-us/azure/api-management/api-management-api-import-restrictions" rel="nofollow noreferrer">here</a> which suggests there's a way to differentiate between operations based on query parameters:</p>
  
  <blockquote>
    <p>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. <strong>However, in API Management
    we allow operations to be discriminated by both path and query
    parameters</strong> (which OpenAPI doesn't support). That's why we require
    parameter names to be unique within the entire URL template.)</p>
  </blockquote>
  
  <p>I have an ApiController that defines two different Get operations, differing only by the query parameters. How do I represent that in my APIM API?</p>