API Reference

Retrieve a native FLUX image task

Retrieve a native FLUX image task. The following is this gateway’s public contract.

GET https://api.tu-zi.com/flux/v1/get_result
Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

Retrieve a native FLUX image task

Updated · Reviewed

Endpoint and authentication

GET https://api.tu-zi.com/flux/v1/get_result

Transport: json

Use an inference API key. Examples contain placeholders; read credentials from environment variables.

Authorization: Bearer YOUR_API_KEY

Before running

Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.

Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.

Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.

Constraints

Queries native flux-3-image asynchronous tasks only. Unknown, foreign or other-protocol tasks return 404; missing id returns 400. Back off while Pending, download result.sample when Ready, and stop on Error.

Query parameters

FieldTypeRequiredDescription / constraints
idstringYesid returned by FLUX submission. Example: YOUR_TASK_ID

Response fields

FieldTypeDescription / constraints
idstringGateway task ID.
statusstringPending, Ready or Error.
result.samplestringImage URL when Ready.
errorstringFailure reason when Error.

Illustrative response; some endpoints show essential fields only. Optional fields may be absent.

{
  "id": "task_example",
  "status": "Pending",
  "result": null
}

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.

Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.