Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Nice catch. I know I was missing something! :) Commented Sep 12, 2012 at 1:54
  • 1
    This seems to bite me EVERY SINGLE TIME I come back to Web API development. I wish Swashbuckle would do something to make sure it and Web API were in sync with their assumptions on whether this data comes/goes over as querystring data or body data. And I wish Web API would NOT assume complex types were read from the Body on GET calls - that makes no sense ever and especially not as a default. Thanks Tohid and @Filip - this question has saved me numerous times! Commented Nov 8, 2016 at 19:25
  • Link is no longer current, but it seems that the default parameter binding method expects the object properties to be passed as the URL parameters, this link is working (for the moment): learn.microsoft.com/en-us/aspnet/web-api/overview/… Commented Oct 14, 2021 at 13:35