<![CDATA[Community at DMM4: Luman]]>https://community.dmm4.ca/s/lumanhttps://substackcdn.com/image/fetch/$s_!ri1f!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6196b18c-13f4-4e0b-8039-53d7b2430b93_512x512.pngCommunity at DMM4: Lumanhttps://community.dmm4.ca/s/lumanSubstackThu, 30 Apr 2026 16:30:14 GMT<![CDATA[Troubleshooting Luman: Decoding API Errors]]>https://community.dmm4.ca/p/troubleshooting-luman-decoding-apihttps://community.dmm4.ca/p/troubleshooting-luman-decoding-apiThu, 02 Apr 2026 03:36:09 GMTIf 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 localhost and luman.ca to 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.

]]>