Ideogram 4.0 API: request shape and what Sume lists

Ideogram 4.0 has its own endpoint with text_prompt or json_prompt. Sume's image catalog lists Ideogram V3 only; here is how the two differ.

4 min readSume
All posts

Ideogram 4.0 is called through its own endpoint, POST https://api.ideogram.ai/v1/ideogram-v4/generate, and Sume's image catalog does not list it. What Sume lists is ideogram/ideogram-v3, so use that id on POST /v1/images.

Ideogram's side comes from its 4.0 reference and 3.0 reference; Sume's from the Image API docs and the catalog code. All read 2026-09-29.

What does the Ideogram 4.0 request look like?

The 4.0 reference takes a text_prompt (natural language, with magic prompt enabled automatically) or a json_prompt (a structured prompt that skips magic prompt). The two are mutually exclusive. It also takes a resolution and a rendering_speed. FLASH is listed as coming soon and currently returns a 400.

Ideogram's older 3.0 endpoint uses aspect_ratio, num_images from 1 to 8 and rendering_speed values FLASH, TURBO, DEFAULT and QUALITY.

Ideogram 4.0 vs 3.0 request fields as Ideogram documents them, read 2026-09-29. Sources: 4.0 reference, 3.0 reference.
FieldIdeogram 4.0Ideogram 3.0
Prompttext_prompt or json_promptprompt
Shaperesolutionaspect_ratio or resolution, not both
Speedrendering_speed (FLASH returns 400 for now)rendering_speed: FLASH, TURBO, DEFAULT, QUALITY
Images per callNot listed in the referencenum_images 1-8

Is Ideogram 4.0 on Sume?

Not as a listed model today. The catalog is the source of truth, and it is one call to read:

curl "https://api.sume.com/v1/images/models" \
  -H "Authorization: Bearer $SUME_API_KEY"

What can I call on Sume instead?

ideogram/ideogram-v3 takes prompt, aspect_ratio from a list of 15 values (1:3, 3:1, 1:2, 2:1, 9:16, 16:9, 10:16, 16:10, 2:3, 3:2, 3:4, 4:3, 4:5, 5:4, 1:1) and quality of low, medium or high. A parameter the model does not list returns 400 unsupported_parameter, so text_prompt, json_prompt and rendering_speed are not accepted. One image is estimated at $0.08 on Sume.

curl -X POST https://api.sume.com/v1/images \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "ideogram/ideogram-v3",
    "prompt": "A poster that reads OPEN LATE in bold red letters",
    "aspect_ratio": "4:5",
    "quality": "high"
  }'

How do I port a 4.0 request to Sume's V3?

Map the fields by meaning, not by name. Put the natural-language text from text_prompt into Sume's prompt. A json_prompt has no equivalent, so flatten its subject, style and layout notes into one written prompt. Replace resolution with the nearest aspect_ratio from the list above, and replace rendering_speed with quality.

Expect different images, not the same image at another address: 4.0 and V3 are different models, and Sume does not promise identical output between them. Run a few prompts through both before you switch anything in production.

Do the image links last?

Ideogram's 4.0 reference says image links are available only for a limited period. Sume returns signed, Sume-hosted URLs, and the same rule applies to you: copy any file you plan to keep into your own storage instead of storing the link.

Will Sume add Ideogram 4.0?

The docs make no promise either way, so this post makes none. When a model reaches the catalog it appears in GET /v1/images/models with its parameters and its price.

Sources

Related posts

More in Models

All Models posts

Written by Sume