If that middleware could be the last in the chain, it could be attached to the resource itself. Since that's not your case, there most reasonable option is to create a compiled middleware and include it as one of the first in the main chain: https://cljdoc.org/d/metosin/reitit/0.7.0-alpha4/doc/ring/compiling-middleware The boolean parameter that you describe can be used as :middleware [[wrap true]], but it will be just a parameter to the middleware function - it won't help you conditionally enable it for specific endpoints. Another, less direct, approach is to transform the middleware chain with a transformer. But if compiled middleware works for you (I don't see a reason why it wouldn't), you should use that instead.

I’ll try the compiled middleware, I just wasn’t aware I could apply it in the stack of app middleware as well as on a specific endpoint. I guess it’s no difference, it’s data all the way down.

But I still thought the boolean parameter could have conditionalized the behavior in each endpoint, even if it ended up called for each one of them

The boolean parameter is there just for convenience, AFAICT [wrap true] is not different from #(wrap % true). So that boolean arg will be static, you won't be able to make it conditional based on the resource or anything else. You can make a middleware conditional based on some data in the request, but that would be logic internal to the middleware itself.

OK got it. That makes sense.

That did the trick! Thanks!