So I figured I can (slurp) that object, however that yields an empty string. Probably because, as I just learned, Output streams can be read only once... And I'm guessing the stream is read throughout all the other interceptors that get the json params for example.

You may want to use the body-params interceptor: http://pedestal.io/api/io.pedestal.http.body-params.html#var-body-params

docs: http://pedestal.io/reference/parameters#_body_parameters

you may want to not use body-param interceptor body parameter interceptor will not provide access to the raw body you probably need something like this:

(def my-json-interceptor
  {:name  ::my-json-interceptor
   :enter (fn [{:keys [request]
                :as   ctx}]
            (if
              ;; maybe check if method=post and content-type=json
              (-> request :request-method 
                #{:post :put '...})
              (let [raw-body-str (-> request :body slurp)
                    json-params (json/parse-string raw-body-str true)]
                (-> ctx
                  (assoc-in [:request :json-params] json-params)
                  (assoc-in [:request :raw-body-str] raw-body-str)))
              ctx))})

Ahhh ok so for this one route, I should probably not use the default interceptors? So I probably shouldn't put it in my service map then, as that would apply to every route..

thanks @U2J4FRT2T, @UDXEK491P, let me try these...

Ok, this seems to be working! Now I'm able to get that raw body string and validate it with the stripe webhook secret key, whew. And still can get the json params to proceed with actually handling the events was able to remove the body-params interceptor from the service map, and move that into the other function I had which added a bunch of interceptors, but only for the routes that need that, instead of all routes.

thanks for the tips/direction, that was straightforward enough 🙂

ok I didn't need to refactor all that but it helped me simplify a few things sooo it's ok, I think

Btw, do not use slurp in prod. Check HttpInputBody docs to see how to read properly

Will do!

@U2J4FRT2T could you help with some pointers where I can read more about both of those? (why not use slurp in prod.. and how to read from an HttpInputBody ?)

slurp is a easy, but not so simple tool I see slurp as a "dev helper" function. For prod, I'd write a function like this

(defn req-body->str 
  [{:keys [^InputStream body]}]
  (String. (.readAllBytes body)))

ahh ok, so because the body object is a subclass of an InputStream (can't remember how I figured that out a week ago), then I can use the methods of InputStream to access it, rather than search through Jetty docs to figure that out. Got it! Thanks @U2J4FRT2T