Just to clarify, when you say parameter, you mean the dynamic binding kind, right? I’ve implemented all the other suggestions. The docs should update soon. Thanks again!

Yes. I was thinking of a parameter and a keyword argument for session-request that defaults to the value of the parameter

Also, I’m really looking forward to throwing away a bunch of code by using this

<https://github.com/Bogdanp/racket-sentry/blob/master/sentry-lib/sentry.rkt#L102-L147|So am I!> :smile:

I’m wondering if it’s worth making the #:data , #:form and #:json keyword arguments mutually-exclusive. Right now, json takes precedence over form which takes precedence over data.

I think mutually exclusive makes sense