+1 on this. Would be great to require auth for certain paths but not all. /cc @logankilpatrick
@rs for now this might provide a workaround: Consistent conversation id in a header?
I haven’t tested this myself so take it with a HUGE grain of salt. But in theory you could make certain path return 401 Unauthorized with a link to login. Once the user is logged in, record the conversation_id or the user_id and link it with the auth token on your server side. Future calls will just use the conversation_id/user_id as a proxy for the auth token