The code looks something like this (this is slightly simplified from what I'm actually doing, but the core logic is here):

(let [health-endpoint #{["/health" :get (fn health [_] {:status 200 :headers {} :body "true"}) :route-name ::health]}]
  (-> schema/load-schema
      (lp/default-service {:port 8000 :host "localhost"})
      (update ::http/routes #(into % health-endpoint))
      http/default-interceptors
      (update ::http/interceptors
              into
              [http/json-body
               (auth/jwt-authentication-interceptor)])))

I'm fairly new to lacinia and pedestal, so I'm probably missing something obvious here...

The jwt-authentication-interceptor looks something like this (again, slightly simplified...):

(defn jwt-authentication-interceptor
  []
  (interceptor/before
   ::jwt-authentication
   (fn [ctx]
     (authenticate ctx))))

This is a case where you just don't use the default-service function; as documented, it's initial scaffolding but you will want to unpack it into your application's code so that you can customize what it does ... in this case, putting the auth interceptor into the /api route rather into the service's default interceptors (which puts auth before routing).

Awesome thanks! I literally have the default-service function pulled up in my editor now to see how it works, I'll pull that logic out and modify as needed 🙂

Alrighty, after a bit of hacking around I got it working! Now to clean it all up... Thanks again @U04VDKC4G

I've burned myself and many others by trying to create things that are both simple and endlessly customizable. In the end, you needed to internalize so much of the internals of such systems to be able to customize them that it was less work for everyone involved to do as we do here: use it initially, then cut-and-paste-and-modify.

Yeah, I can imagine that being a pretty challenging issue working on an OSS project like this -- trying to maintain the delicate balance between generality and specificity