Old image ids like nano-banana-2 still work on Sume /v1/images
Sume accepts bare Image Router ids like gpt-image-2 and nano-banana-2 as aliases for org/slug ids on POST /v1/images. Check the list; the Gemini 2.5 id is gone.
POST /v1/images accepts the bare Image Router ids, for example gpt-image-2 and nano-banana-2, as aliases for their org/slug catalog equivalents. That lets an older integration keep its model strings while it moves off POST /v1/image-router/generate. Google's gemini-2.5-flash-image is shut down, so do not rely on it.
Two spellings, one model
The catalog on GET /v1/images/models lists ids like bytedance-seed/seedream-4.5. The Image API doc states that legacy bare ids are accepted as aliases. New code should send the org/slug id because that is what the catalog returns, and it reads unambiguously in logs.
Video is different: /v1/videos accepts bare catalog ids only, such as seedance-2. An org/slug id sent to a video route is not a catalog id.
What to do with the old route
POST /v1/image-router/generate and GET /v1/image-router/models still work unchanged, but they are deprecated and will not get new parameters. The Image API replaces them. Moving means three changes.
- Send the request to
POST /v1/imagesinstead of the Image Router generate route. - Handle
200withdata[].url, and202with a job envelope when the wait passes 30 seconds. - Stop expecting inline base64. Sume returns signed, Sume-hosted URLs, so download them.
Confirm with the catalog
Aliases can be retired, so confirm before a release. List the models, check that the id you plan to send is present, and read its supported parameters.
The Google deprecations page names gemini-3.1-flash-image-preview as the vendor's replacement for the shut-down model (Gemini deprecations, read 2026-10-05). Whether Sume lists a matching id is a question for GET /v1/images/models, not for this post.
curl "https://api.sume.com/v1/images/models" \
-H "Authorization: Bearer $SUME_API_KEY"Sources
Related posts
More in Developers
- Nano Banana 2 Lite's 10 aspect ratios: what to send for 4:5
Lite accepts 10 ratios including 4:5 and 21:9. On Sume, Instagram 1080x1350 is aspect_ratio 4:5, and Nano Banana Pro or 2 list it; Imagen and Grok do not.
- Nano Banana 2 reference slots (10+4+3) vs Sume's flat reference list
Google splits Nano Banana 2 references into 10 object, 4 character and 3 style slots. Sume's input_references is one flat list capped at 10, with no slots.
- Nano Banana 2 thinking_level minimal or high: not on Sume
Google offers thinking_level minimal or high on the Nano Banana 2 variants. Sume's Image API has no such field, so sending it returns 400 unsupported_parameter.
- Native audio in stitched AI clips: which Sume models force it
Gemini Omni Flash 1.1 always makes audio, H3 Max adds stereo, Seedance 2 can. A stitched Timeline render takes its audio from the spine, so plan the sound.
Written by Sume