title: Can an ASP.NET WebAPI action parameter be excluded from Swashbuckle/Swagger UI?
body: <p>My actual case is I've allowed dependency injection using parameter binding on API controllers implementing a custom parameter binding.</p>
  
  <p>For example, a controller action may look as follows:</p>
  
  <pre><code>public async Task&lt;IHttpActionResult&gt; GetByIdAsync(Guid id, ICustomerFacade customerFacade)
  </code></pre>
  
  <p>When I explore my API using Swagger UI generated by Swashbuckle, <code>customerFacade</code> is specified as an actual and required resource action parameter.</p>
  
  <p>Do you know any way of excluding controller action parameters from generated Swagger UI?</p>
  
  <p><em>Note: I know that a workaround could be injecting dependencies using constructor injection, but I still prefer to be able to both do constructor and regular method dependency injection.</em></p>