-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the new API URLs and deprecate the old endpoints #27
Comments
Hi @RobotSail, are you going to update the I got an email from OpenAI this morning about the changes they made: Hi there, Thanks for being a user of OpenAI’s moderations endpoint! I’m writing to inform you about the following breaking change in our API. Starting Friday, August 5th 2022, the type of moderation endpoint response fields If your application relies on these fields being integers, please update your code to rely on booleans. Otherwise no action is required on your end. Please reach out to support@openai.com if you have any concerns with this change. Thanks!
Best, |
@RobotSail thank you for the PR! 🙌🏻 The mock server is also really welcome here. Previously this repo was declined from the awesome-go list due to a lack of mock server testing. |
OpenAI's API has recently changed so API calls are made to endpoints such as
/v1/completions
for completions instead of/v1/engines/${engineID}/completions
.I'm currently migrating to using go-gpt3 instead of my own client, and would like to incorporate a mock server for simulating responses. This would be incredibly helpful to avoid handling the old API.
The text was updated successfully, but these errors were encountered: