Error When Making API Call to OpenAI via Bubble: Error Code 1015

Hello everyone,

I’m encountering a persistent issue when making API calls to OpenAI through the Bubble platform. When I execute the call manually via the terminal, everything works fine. However, when I use Bubble’s API connector, I receive the following error:

Raw response for the API
Status code: 429
error code: 1015

This issue started yesterday, and I’m unsure what else can be done to resolve it. It seems to be related to rate limits or the frequency of requests, but I haven’t found precise information in the documentation.

Attached below are screenshots of the settings and the actual error (included in the post). I would appreciate any help or guidance from anyone who has faced a similar issue or understands what might be going wrong.

Thanks in advance to anyone who can offer assistance!

You are sending too many request.

Check OpenAI error description:
429 - You exceeded your current quota, please check your plan and billing details Cause: You have run out of credits or hit your maximum monthly spend.
Solution: Buy more credits or learn how to increase your limits.

Edit: I forgot, But Bubble itself may be “rate limited” because of all app that are making request from Bubble server. You can find other topics about that.

same issue here. All of us had the ex<ct problem a month ago…

1 Like

Do you think it’s happening again now?
Are there other people with the same problem,So that means all we have left to do is sit and wait for them to fix it

I don’t say it will fix this issue, but you could try something. Since a few months, Bubble now add automatically the user-agent header. Try to add your own
example: user-agent: bubble.io/yourappname or just yourappname. Depending of the setting on OpenAI server, it may be enough to solve this issue.

I am also facing this issue with DALLE. 1015 error. Only work around the team feasible with this image generator would be going through a third-party service which would be more costly and slower for the end-user. We will probably need to switch to a different image generator if this persists.