/v1/images/edits rejects gpt-image-2 — hardcoded to dall-e-2 only
The /v1/images/edits endpoint rejects gpt-image-2 with a 400 error.
Error returned: { “error”: { “message”: “Invalid value: ‘gpt-image-2’. Value must be ‘dall-e-2’.”, “type”: “invalid_request_error”, “param”: “model”, “code”: “invalid_value” } }
Tested models — ALL rejected:
- gpt-image-2 – primary concern
- gpt-image-1
- gpt-image-1-mini
- chatgpt-image-latest
- image-latest
Only dall-e-2 is accepted, which is the oldest and lowest-quality model.
This means gpt-image-2, your most capable image model, cannot accept image input at all. The /v1/images/generations endpoint (text-only) accepts gpt-image-2 fine, but /v1/images/edits does not. There is no way to feed a reference image into gpt-image-2 through any available endpoint.
Request format tested: multipart/form-data with binary image bytes, proper Content-Type and filename headers — same format that works with dall-e-2.
Discussion in the ATmosphere