@psalaberria002 you can set the response coercion separately, which effects the whole api/context/endpoint. So, if you could cook up a Schema Matcher that does loose validation, that would work. The guide how to set the customer coercion (with 2.0.0.*) is here: https://github.com/metosin/compojure-api/wiki/Coercion#custom-schema-coercion

How to actually create a Matcher that allows extra keys…. maybe #schema could help? Jason is really helpful, if you want to write an issue about that into Schema issues (https://github.com/plumatic/schema/issues)

… and you can always turn off the response coercion, but I guess that’s not what you would like to get…

@ikitommi thank you. I will give it a try.