[oAuth and GPT Actions] - 5 things I have learned (oAuth only)

[KimSia]

@fluxgill

@KimSia Is there anyway a custom GPT once published can be used by different users with different API keys to talk to an API service? these users might have api service running in different servers but all of them will be using same endpoints.

I’m unsure what you mean exactly. can you do a loom to show us?

Easier to debug.

In any case, here’s what I do know.

You have a custom GPT (let’s call this GPT-Alice) talking to your server using oAuth.

Let’s also say you have two different users called Bob, and Carol using GPT-Alice and they both have accounts on your server.

When Bob and Carol interact with GPT-Alice, and GPT-ALice needs to send info to your server on oAuth protected endpoints, GPT-Alice will prompt Bob and Carol to login using oAuth.

So Bob and Carol login as per normal.

There’s no different API key.

However, GPT-Alice needs to have its own client ID and client secret generated by your server.

See the Part 5 video at [oAuth and GPT Actions] - 5 things I have learned (oAuth only) - #11 by KimSia for more details