DALL-E 3 API removed May 12, 2026: GPT Image ids on Sume
OpenAI removed dall-e-3 from its API on May 12, 2026 and points to gpt-image-2. On Sume, send openai/gpt-image-2 to POST /v1/images instead.

The DALL-E 3 API no longer exists: OpenAI's changelog says dall-e-2 and dall-e-3 were deprecated and removed from the API on May 12, 2026, and recommends gpt-image-2, gpt-image-1 or gpt-image-1-mini. Sume has no DALL-E id. A client that used DALL-E 3 can send openai/gpt-image-2 to POST /v1/images.
OpenAI facts are from its API changelog (read 2026-09-30; the entry is older than 60 days). Sume facts are from the Image API docs.
What replaces the model id?
On Sume, ChatGPT Image 2.5 is openai/gpt-image-2.5 (Flare) and openai/gpt-image-2.5-sunburst, and the docs say ChatGPT Image 2 remains selectable. The bare legacy ids such as gpt-image-2 are still accepted as aliases for their org/slug forms. See the 2 vs 2.5 migration.
| Id | Where it stands |
|---|---|
dall-e-3, dall-e-2 | Removed from OpenAI's API May 12, 2026 |
gpt-image-2, gpt-image-1, gpt-image-1-mini | OpenAI's recommended replacements |
openai/gpt-image-2 | Selectable on Sume |
openai/gpt-image-2.5 | ChatGPT Image 2.5 on Sume |
What does the Sume request look like?
Post JSON with model and prompt. Quality is auto, low, medium, high, xhigh or max, subject to the model's catalog.
const res = await fetch("https://api.sume.com/v1/images", {
method: "POST",
headers: {
Authorization: "Bearer " + process.env.SUME_API_KEY,
"Content-Type": "application/json",
},
body: JSON.stringify({
model: "openai/gpt-image-2",
prompt: "a product photo of a ceramic mug",
quality: "high",
output_format: "png",
}),
});
console.log(res.status, await res.json());What comes back, and how is it billed?
Images come back as Sume-hosted URLs. POST /v1/images blocks up to 30 seconds and returns 200; a longer generation returns a 202 job to read later (see long requests). Billing is all-or-nothing per generation: completed is billed in full, failed or cancelled is not.
Do I need to change other parameters?
Possibly. Sume rejects a parameter the selected model does not list with 400 unsupported_parameter, so read the catalog's supported_parameters rather than carrying DALL-E fields over unchanged.
Sources
Related posts
More in Models
- Kazakh speech to text API: Nova-3 and Sume language_code
Deepgram added Kazakh to Nova-3 on Sep 3, 2026. Sume STT 1.0 takes an optional language_code hint, or auto-detect. How to send audio and check the output.
- FLUX video edit API: 720p downscale, and video_url edits on Sume
BFL's edit-a-video endpoint downscales sources above 720p. Sume lists no FLUX video; its edit path is video_url with gemini-omni-flash-1.1 only.
- gemini-2.5-flash-image shutdown on October 2, 2026
Google lists gemini-2.5-flash-image for shutdown on October 2, 2026. Sume lists Nano Banana 2 and Pro under google/ ids to move image requests to.
- Gemini 3.5 Transcribe API limits: 1 hour vs Sume STT's 10 minutes
Gemini 3.5 Transcribe takes up to 1 hour per request, 30 minutes with diarization or word timestamps. Sume STT takes 600 seconds; split longer audio.
Written by Sume