🐛 Bug: Handle Quota Usage for APIs

[jaspermayone]

📋 Description

When the application exceeds the quota limit for an external API, it currently crashes. This issue proposes a more graceful handling strategy: ignore the failed request and log a warning, rather than allowing the entire app to crash.

---

✅ Expected Behavior

• When an API quota is exceeded:
  • The app should not crash.
  • The failed request should be skipped or deferred.
  • A warning should be logged for observability.

---

🧪 Steps to Reproduce

1. Simulate or trigger an API quota limit (e.g., by mocking a 429 response).
2. Observe that the app crashes instead of handling the error gracefully.

---

💡 Suggested Fix

• Wrap API calls in a try/catch or error-handling block.
• Detect quota-related errors (e.g., HTTP 429 or specific error codes).
• Log a warning and skip the request.
• Optionally, implement a backoff or retry mechanism if appropriate.

---

🛠 Development Notes

• A temporary fix was added in commit [0ccae72](https://github.com/phish-directory/api/commit/0ccae72), but a more robust solution is needed.
• This issue is suitable for newcomers and is part of our effort to improve error resilience.

---

📎 Related

• [Commit 0ccae72](0ccae72) – Temporary fix reference