You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means that, if different requests need to be associated to different users, the request header needs to be dynamic and change on each request (and therefore we need to create a new Configuration object on each request).
However, OpenAI API already accepts a user field in the body of the request, which has a similar purpose.
It would be handy to optionally get the userId for LLM Report from this field of the request body, rather than the X-User-Id header. This would avoid having to set new headers for each request.
The text was updated successfully, but these errors were encountered:
Currently the
userId
for a specific request is set through theX-User-Id
header, like this:This means that, if different requests need to be associated to different users, the request header needs to be dynamic and change on each request (and therefore we need to create a new
Configuration
object on each request).However, OpenAI API already accepts a
user
field in the body of the request, which has a similar purpose.It would be handy to optionally get the userId for LLM Report from this field of the request body, rather than the
X-User-Id
header. This would avoid having to set new headers for each request.The text was updated successfully, but these errors were encountered: