Maybe I misunderstood – are you asking what’s the right way to define a reusable (single) parameter, or whether there’s a way to group a number of parameters and reference them as a whole group once in different paths?
On 12/06/2017, 13:41, "'Philipp' via Swagger" <[email protected]> wrote: I know, that's why I tried to use a body parameter with a schema/object definition as you can see in my second example. But till now I am not able to write a definition which the editor accepts when I define the parameter outside the path/request. If I place it into the request everything is fine. But I do not like this solution because I have to define the same parameter for every request again and again. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
