+1Hello!
My company’s has a custom ChatGPT endpoint. When I try to connect, Lucid is sending the authorization as:
Bearer <API key>
But we’re expecting a custom key (starting with another term instead of “Bearer”).
Is there a way to change the authorization to a custom key?
+23Hi
+1Hi
+8Hi
As a workaround, you might consider implementing a script on your end that can modify the incoming authorization header to suit your company’s custom endpoint's requirements.
We apologize for any inconvenience this might cause. Your feedback is important to us, and I've shared your concerns directly with our Product team for future consideration.
Regarding your idea for a custom endpoint option, we encourage you to engage with our Product Feedback Community space. Please first search the Product Feedback section (with the filter Topic Type = Idea) to see if your idea has already been submitted. If you find a similar idea, feel free to add your details and upvote it, as this helps us consolidate and understand the popularity of specific requests. If your idea hasn’t been suggested yet, please create a new post including details about your use case and what you’d like to see. This allows other users with similar needs to discover and support your idea.
For more information on how Lucid manages feedback via this community, take a look at this post: Feedback and Feature Requests | Community.
A Lucid account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.
A Lucid account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
