ideogram-common-errors

# Ideogram Common Errors ## Overview Quick reference for the most common Ideogram API errors, their root causes, and proven fixes. All Ideogram endpoints return standard HTTP status codes with JSON error bodies. ## Prerequisites - Ideogram API key configured - Access to request/response logs - `curl` available for manual testing ## Error Reference ### 401 -- Authentication Failed ``` HTTP 401 Unauthorized ``` **Cause:** Missing, invalid, or revoked API key. **Fix:** ```bash set -euo pipefail # Verify the key is set and not empty echo "Key length: ${#IDEOGRAM_API_KEY}" # Test auth directly curl -s -o /dev/null -w "%{http_code}" \ -X POST https://api.ideogram.ai/generate \ -H "Api-Key: $IDEOGRAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{"image_request":{"prompt":"test","model":"V_2_TURBO"}}' ``` **Common mistakes:** - Using `Authorization: Bearer` instead of `Api-Key` header - Whitespace or newlines in the key string - Key was regenerated in dashboard but not updated in `.env` --- ### 422 -- Safety Check Failed ```json {"error": "Prompt or provided image failed the safety checks"} ``` **Cause:** Prompt text or uploaded image triggered Ideogram's content filter. **Fix:** - Remove brand names, celebrity names, or trademarked terms - Avoid violent, sexual, or politically sensitive content - Remove explicit references to real people - Rephrase with neutral descriptors ```typescript // Pre-screen prompts before sending to API const FLAGGED_PATTERNS = [...