Skip to main content
This walkthrough uses gemini-3.1-flash-image at 1K. It is a practical default for a new integration because the same model can later move to 2K or 4K without changing the request shape. Before you begin, create a development key in the YingTu console and review authentication safety. Run the code on a server or local development machine, not in browser-delivered application code.

Send the request

cURL
The request is billable. Keep candidateCount omitted or set to 1; send separate requests when you need separate images.

Save the image in Python

Do not assume the image is parts[0] or that it is always PNG. The response may use PNG, JPEG, or WebP and may place a text part before the image; always scan the complete parts array and use the returned MIME type.

The same parser in Node.js

Choose another model

Compare the current 1K, multi-resolution, premium, and migration paths.

Move work to a task

Submit the same body and retrieve the result after the connection ends.

Diagnose failures

Distinguish validation, authentication, balance, rate-limit, and server errors.

Check SDK support

Use the maintained REST path without assuming an SDK is compatible.
Last modified on September 2, 2026