Troubleshooting Luman: Decoding API Errors
A guide to handling HTTP status codes and common integration hurdles.
If the Luman engine hits a snag, it provides clear HTTP status codes to help you debug quickly. Understanding these “red flags” is key to a smooth implementation.
⛔ 403 Forbidden: The Domain Lock Barrier
This is the most frequent hurdle. It occurs when your Domain Lock is active, but the current request domain isn’t authorized.
The Fix: If your images are failing in your local dev environment or on the Luman Dashboard itself, ensure you have added
localhostandluman.cato your authorized domains.
⏳ 429 Too Many Requests: Plan Limits
This error indicates you have reached your rate limit (3 images/sec) or your monthly plan quota (e.g., 5 Credits for Free users).
The Fix: Upgrading to a Pro or other tier in your dashboard will lift these limits immediately.
⚠️ 400 Bad Request: Missing Data
The Luman engine is simple, but it needs the basics. If you see a 400 error, you are likely missing a required parameter—most commonly the title.