Today, OpenAI added additional Cloudflare protections that make it more difficult to access the unofficial API. _This is affecting all ChatGPT API wrappers at the moment_, including the Python ones. See [this issue](https://github.com/transitive-bullshit/chatgpt-api/issues/96).
Yesterday, OpenAI added additional Cloudflare protections that make it more difficult to access the unofficial API.
**As a temporary workaround**, make sure you're using the latest version of this package and Node.js >= 18:
The demos have been updated to use Puppeteer to log in to ChatGPT and extract the Cloudflare `cf_clearance` cookie and OpenAI session token. 🔥
1. Log into https://chat.openai.com/chat and copy a fresh session token (same instructions as below).
To use the updated version, first make sure you're using the latest version of this package and Node.js >= 18:
2. Copy the value of the `cf_clearance` cookie and store it in a `CLEARANCE_TOKEN` environment variable in addition to your `SESSION_TOKEN`.
3. Copy your browser's `user-agent` header from any request in your browser's network tab.
4. Use both tokens when creating the API wrapper:
```ts
```ts
constapi=newChatGPTApI({
constapi=newChatGPTApI({
sessionToken:process.env.SESSION_TOKEN,
sessionToken:process.env.SESSION_TOKEN,
clearanceToken:process.env.CLEARANCE_TOKEN,
clearanceToken:process.env.CLEARANCE_TOKEN,
userAgent:''// replace to match your real browser's user agent
userAgent:''// needs to match your browser's user agent
})
})
awaitapi.ensureAuth()
awaitapi.ensureAuth()
...
@@ -24,9 +18,10 @@ await api.ensureAuth()
...
@@ -24,9 +18,10 @@ await api.ensureAuth()
Restrictions on this method:
Restrictions on this method:
- Cloudflare `cf_clearance`**tokens expire after 2 hours**, so right now you'll have to manually log in and extract it by hand every so often
- Cloudflare `cf_clearance`**tokens expire after 2 hours**, so right now we recommend that you refresh your `cf_clearance` token every ~45 minutes or so.
- Your `user-agent` and `IP address`**must match** from the real browser window you're logged in with to the one you're using for `ChatGPTAPI`.
- Your `user-agent` and `IP address`**must match** from the real browser window you're logged in with to the one you're using for `ChatGPTAPI`.
- This means that you currently can't log in with your laptop and then run the bot on a server or proxy somewhere.
- This means that you currently can't log in with your laptop and then run the bot on a server or proxy somewhere.
- Cloudflare will still sometimes ask you to complete a CAPTCHA, so you may need to keep an eye on it and manually resolve the CAPTCHA. Automated CAPTCHA bypass is a WIP.
- You must use `node >= 18`. I'm using `v19.2.0` in my testing, but for some reason, all `fetch` requests using Node.js `v16` and `v17` fail at the moment (these use `undici` under the hood, whereas Node.js v18 and above use a built-in `fetch` based on `undici`).
- You must use `node >= 18`. I'm using `v19.2.0` in my testing, but for some reason, all `fetch` requests using Node.js `v16` and `v17` fail at the moment (these use `undici` under the hood, whereas Node.js v18 and above use a built-in `fetch` based on `undici`).
- You should not be using this account while the bot is using it, because that browser window may refresh one of your tokens and invalidate the bot's session.
- You should not be using this account while the bot is using it, because that browser window may refresh one of your tokens and invalidate the bot's session.
