Moderation API - Error: 429 Too Many Requests - 'invalid_request_error'

API
1

Hey there, I’m trying to use the omni-moderation-latest model to moderate image content for my project. I read the docs, specifically the examples for image and text moderation..

Whenever I try to make a request I get an Error: 429 Too Many Requests. I have tried using just the text model, and the result is the same. If I provide an invalid image url the error instead indicates that the image couldn’t be downloaded, so I am confident the url is not the problem.

I browsed the forum for this topic and learned that this was likely because I did not have a positive credit balance. I purchased credit yesterday and generated a new API key, but the error persists. I can see that the API key’s last used field is updated when the request fails, so at the very least it is processing with the correct key even if it doesn’t work and there are no logs.

The error type is ‘invalid_request_error’ which makes me think it might not actually be a rate limiting issue. I get request IDs logged in console but there are no actual logs in my OpenAI dashboard so I’m not sure how to proceed to get more information. Has anyone else run into this problem before?

Here is a code excerpt that produces the error that very closely resembles the example from the docs

         // The only difference between mine and the example is that I add my API key
        const openai = new OpenAI({
            apiKey: process.env.OPENAI_API_KEY
        });

        const moderation = await openai.moderations.create({
            model: "omni-moderation-latest",
            input: [
                { type: "text", text: "...text to classify goes here..." },
                {
                    type: "image_url",
                    image_url: {
                        url: imageUrl,
                    }
                }
            ]
        });

I am making just a single request each attempt.

1 Like
2

Strange, might be a bug.

When you put credits the system upgraded your tier or are you still in the free tier?

Does the omni-moderation-latest show in your limits page?

3

I was upgraded to tier 1 when I added credits. My limits page does show the omni-moderation-latest model for both organizaiton limits and my project limits.

4

When did you make the credit addition? If it’s less than 25 hours then it’s worth waiting for the system to update. If it’s longer than that, can you make API calls of ANY kind?

5

It has been more than 48 hours, I tried generating a new key today to see if it would make a difference but I still get the 429 error.

I tried a basic chat completion request to gpt-3.5-turbo and I got another 429 error, though now I get an ‘insufficient quota type’ instead of ‘invalid request’. This is also listed as an allowed model for the organization and project.

6

Did you give the API key the right permissions?

Showing credits available for you?

7

Yes, the key has full permissions. The credits are marked ‘Available’ in my credit grants, I see the balance listed in my billing overview, and the invoice from when I added the balance is listed as ‘paid’ in my billing history.

I did send an email to support@openai.com earlier along with some of the request IDs, since I was having a hard time not getting my support requests intercepted by the chatbot in the help section. I will update here with context if they are able to resolve the issue.

8

I know it was confusing in the past… Are you sure the credits aren’t expired?

Is it just the moderation model? What image model are you trying to use? Are you aware of Usage Tiers and rate limits?

Yeah, please let us know. Good luck.

9

Ditto. The documentation says free and it just simply does not work. Reset the key, created a brand new account, waited many days - still the same issue. No help from support either.

10

I don’t know if this will help you but I found this forum post where someone was able to resolve the error by making a new project. I noticed my project also said it was created in September 2024 despite being created a few days ago, so I tried the same fix. It did not resolve the issue for me unfortunately but YMMV.

1 Like