Has anyone else faced relentless API restrictions on Daybreak Blue recently?

I've been grinding on the same project for four months now. Usually, the restriction notices pop up every once in a while, but for the last couple of days, it's been non-stop — literally every minute. I'm completely stuck; I can't make any progress whatsoever. I'm guessing they might have cranked up the API guardrails or something in the system changed. I reached out to their support team, and their response pointed towards potential throttling issues, suggesting my request rate might be hitting their limits more often.
The restrictions seem to be hitting without any clear rhyme or reason. It's not just random; it feels like a systematic change. Has anyone else noticed this surge in restrictions? I'm starting to think it's more than just a temporary glitch. What should I do when these restrictions lock me out? Is there a way to adjust my request patterns to avoid hitting the limit so frequently? Or should I just keep waiting for Daybreak Blue to sort it out on their end?
Here's the prompt I've been using, which might offer some insights:

Act as an API error analyst. Given the error message "Rate limit exceeded for user 'your_username'", provide a step-by-step guide on how to mitigate this issue for the Daybreak Blue API. Include suggestions for adjusting request intervals, using caching mechanisms, and implementing backoff strategies. Explain how these methods can help reduce the frequency of encountering the "Rate limit exceeded" error.

The prompt is designed to get specific advice on handling the rate limit issue. The response should ideally provide actionable steps to reduce the frequency of these restrictions. I've been testing different intervals and caching methods, but nothing seems to make a significant difference. It's either too much traffic or an issue on their side.
One thing I've noticed is that the error messages are consistent. Every time I hit the limit, it's the same message: "Rate limit exceeded for user 'your_username'". This consistency suggests that the issue might be on my end, but it could also be a server-side problem. The support team mentioned that they sometimes adjust the limits based on overall usage patterns, so it could be that the overall traffic has increased, making the current limits too tight for many users.
Another angle I'm exploring is whether there are any alternative endpoints or methods to access the data I need. Sometimes, switching to a different API endpoint can bypass certain restrictions. I've checked the documentation but haven't found any obvious alternatives. If there are other endpoints or methods I should be aware of, that could be a potential solution.
Here’s a breakdown of what I’ve tried so far:

1. Reducing Request Frequency: I've tried lowering the number of requests per minute. This hasn't made a significant difference, but it has slightly reduced the frequency of the errors.
2. Implementing Caching: I've added caching mechanisms to store frequently accessed data. This helps, but it doesn't eliminate the issue entirely.
3. Using Backoff Strategies: I've implemented exponential backoff in my code to handle the errors more gracefully. This hasn't reduced the frequency of the errors but has made the system more resilient to them.
4. Contacting Support: As mentioned earlier, I've reached out to Daybreak Blue's support team. They suggested that the issue might be temporary and to keep an eye on it. They also mentioned that they might adjust the limits in the near future.

Given these steps, here’s what I plan to do next:

• Monitor and Adjust: I'll continue to monitor my request patterns and adjust as needed. If the restrictions persist, I might need to implement more aggressive caching strategies.
• Test Different Intervals: I'll experiment with different request intervals to see if there's a sweet spot that minimizes the errors.
• Explore Alternative Endpoints: I'll dig deeper into the API documentation to see if there are any alternative endpoints I can use.
• Keep in Touch with Support: I'll maintain communication with Daybreak Blue's support team to stay updated on any changes they might make to the API.

If anyone else has faced similar issues, I’d love to hear how you handled them. Did you find any specific strategies that worked well? Any insights into whether this is a widespread problem or just a temporary glitch would be incredibly helpful.