API Reference
Retrieve a native FLUX image task
Retrieve a native FLUX image task. The following is this gateway’s public contract.
Preview guide
Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.
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 calling
- Examples use this site's address. For another gateway, replace only the site address and keep the full endpoint path.
- Use an inference key created on this site's token page. Set the
API_KEYenvironment variable or replaceYOUR_API_KEY, as shown in the selected example.
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
| Field | Type | Required | Description / constraints |
|---|---|---|---|
| id | string | Yes | id returned by FLUX submission. Example: YOUR_TASK_ID |
Response fields
| Field | Type | Description / constraints |
|---|---|---|
| id | string | Gateway task ID. |
| status | string | Pending, Ready or Error. |
| result.sample | string | Image URL when Ready. |
| error | string | Failure 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.
兔子API