you can check for any error here
and you can then ask gpt to fix
2 Likes
I don’t think the issue is with the schema. Mine is correct. It’s something to do with the saving of the auth key, or the entire bot. A few times I tried to update the schema, where it seemed to save, but then when I came back it was the previous, former version of my schema. Not surprising as there are probably a lot of saves happening. Or maybe just a bug.
Has anyone gotten an API with bearer auth to work?
1 Like
I do have an API with Bearer working.
But I also have another different domain that do not work. I don’t understand what is happening behind the scene. We need some logs or something.
1 Like
Cool. Would you mind sharing how you have the securitySchemes and security sections of the OpenAPI specs setup for your API? (Don’t share any keys or anything!)
I just would love to know if I have mine setup correctly, as this OpenAPI spec business seems overly complicated.
+1 for logs. Didn’t Sam say something about them in the keynote?
At this point I am just shifting over to the Assistants API. GPTs are cute and all but I feel like I’ll make more progress just rolling my own. At least I’ll have the logs there. 
1 Like
I’m also having issue with saving schema. It seems to have inconsistent version when I try to save the GPT builder.
You can ask it to provide full diagnostic output, it will then show following
which you can click into for details (not shown here for security reasons)
Update: I have only gotten this to work in the GPT preview window.
1 Like
I just told it that it must provide full debug/diagnostics for each Action/API call listing all parameters and values used. Possibly check your GPT’s setup instructions panel and see if their is boilerplate security phrases that block the debugging and remove them…just remember that you may want to block debugging if releasing the GPT to end users
Hello. Is there any way to obscure the call stack of the action? I am wondering about having that out in the open, which exposes the backend server. Anyone have any thoughts on this?
I have tried to connect with a custom API but I am finding it impossible to access the endpoints that are secured with JWT.
I found this out too, the schema is not always updating. Try running it in a new window using the GPT link, it worked for me.
To me “/API/v2/user” works fine, why you escape slash.
Also
“url”:“https:your-endpoints-server.com”
@redfive didn’t work for me. How did you do it ??
I just had my own few daze of “Error…” with no debugging help. My challenge turned out to be I was using NGROK, getting 6204. It took me 2 days to figure this out. With no help from the GPT…no logs…until the GPT finally spewed out 6204 and I could figure it out from there… wow…2 days what normally takes 10 minutes. I truly hope there is an effort in investing into debugging tools.