title: Defining an API with swagger: GET call that uses JSON in parameters
body: <p>I am trying to create a proper, REST API, and document it with Swagger (2.0).</p>
  
  <p>So, I have an API call that is a query, ie, it makes no changes and doesn't create anything (idempotent and safe). But it requires passing in a complex JSON parameter (list of items, 2 or 3 sets of addresses, etc). So I'm doing a GET with a parameter thats URL encoded JSON. That seems like the proper way to do it.</p>
  
  <p>I see so often API's like this where they do it as a POST for this reason, but that's an incorrect use of the POST verb.</p>
  
  <p>I'm seeing lots of swagger API's that do this...</p>
  
  <p>I can't figure out if there's a way to do a proper rest API with Swagger, using a JSON parameter. You can define the parameter as a string, of course, and pass your encoded JSON into it, but then the swagger tooling doesn't understand that there's a schema/definition for it.</p>
  
  <p>Is swagger not able to properly document this kind of call?</p>