When there are multiple parameters in a Resource URI, and at least one with a pct-encoded character the rendered code sample show incorrect URL. Consider following blueprint: Request URL renders fine with: ``` # /notes{?foo%2Ebar} ### POST + Response 201 (application/json) ``` Appending one additional query parameter, let's say `a` results into incorrect URL in the example. Compare (correct):  With incorrect:  Also > The downstream effect here is that the incorrect URI is sent to the API server so the response is malformatted creating an error. Originally reported at [SO](http://stackoverflow.com/questions/28181431/how-can-i-get-multiple-encoded-parameters-into-an-apiary-uri-template/28181772)
When there are multiple parameters in a Resource URI, and at least one with a pct-encoded character the rendered code sample show incorrect URL.
Consider following blueprint:
Request URL renders fine with:
Appending one additional query parameter, let's say
aresults into incorrect URL in the example. Compare (correct):With incorrect:
Also
Originally reported at SO