Skip to main content
POST
  1. After submission, a task_id will be returned. If you provided a callback_url, when the task status becomes finished or failed, a POST request will be sent to the callback_url.
  2. Regardless of whether callback_url is provided, you can retrieve the response result through the unified Query Task Status endpoint.
GPT Image 2.6 Fixed runs GPT Image 2.6 Flare or Sunburst with per-image pricing based on resolution, instead of token-based pricing. Choose the variant with version: Flare is tuned for speed, and Sunburst for more detailed visuals and more precise, consistent edits. Add reference images to edit or guide the output.

Models

  • gpt-image-2.6-fixed — GPT Image 2.6 Flare or Sunburst with per-image pricing

Required parameters

  • prompt (string): Image description, 1–32000 characters.

Optional parameters

  • version (string): flare or sunburst. Default is flare.
  • resolution (string): 1K, 2K, or 4K. Default is 1K.
  • size (string): auto, 1:1, 16:9, 9:16, 4:3, 3:4, 3:2, 2:3, 5:4, 4:5, or 21:9. Default is 1:1.
  • image_urls (array of strings): Up to 16 reference image URLs.

Output

A finished task returns the generated image in files with file_type: image.

Examples

  • Text to image with Flare at 2K — sets prompt, version, resolution, size.
  • Edit with a reference image using Sunburst — sets prompt, version, image_urls.

Notes

  • n and num_images are not supported. Each task returns one image.
  • image_urls must be an array, even for one image.
  • Output is a raster image. Complexity control, SVG output, animated GIF output, and markup-guided edits are not available on this endpoint.

Authorizations

Authorization
string
header
required

All API endpoints require Bearer Token authentication.

Create an API key: sign in to PoYo, open Dashboard → API Key at poyo.ai/dashboard/api-key, and click to create a key.

Add it to the request header:

Body

application/json
model
enum<string>
required

Public model identifier.

Available options:
gpt-image-2.6-fixed
input
object
required
callback_url
string<uri>

Optional webhook URL for task completion or failure notifications.

Response

Task submitted successfully

code
enum<integer>
required

Business status code. 200 means success; any other value means the request failed. Always check this field: some validation errors return HTTP 200 with code: 400 in the body.

  • 200: Success
  • 400: Invalid request parameters
  • 401: Missing or invalid API key
  • 402: Insufficient credits
  • 403: Permission denied
  • 404: Resource not found
  • 408: Request timeout
  • 429: Rate limit exceeded
  • 500: Internal server error
  • 502: Upstream service error
  • 503: Service unavailable

See Error Codes for details.

Available options:
200,
400,
401,
402,
403,
404,
408,
429,
500,
502,
503
Example:

200

data
object
required