GPT Actions requiring multiple custom headers

Description
Some APIs require multiple custom headers for interaction, for example both an Auth Bearer token and an app_id or similar. Actions currently only allow for custom authorization headers and have no option to add additional headers.

Expected behaviour
Users should be able to add multiple headers in addition to Auth on any one action to permit interaction with more complex APIs.

6 Likes

I am trying to call the NotionAPI from a GPT but I am unable to pass the Notion-Version in the header :face_holding_back_tears:

5 Likes

Is this really the only way to submit bugs? Because I suspect a lot of them will be swamped by the forum signal-to-noise ratio.

I’m running into this issue as well. This prevents the development of many custom GPTs because many APIs require an application ID header or some additional header besides the API key.

Hoping someone has found a workaround or a fix is being worked on, but it seems inserting an additional header in the schema is not valid from what I have tried.

I’m using Retool Workflows to wrap my API calls until OpenAI allow us to add custom headers in Actions. Retool has a free tier which allows 500 workflow runs a month. I’m sure OpenAI will extend custom GPTs to be able to include additional headers soon.