API Reference

Retrieve request image or task results

Retrieve image results by request ID. The following is this gateway’s public contract.

GET https://api.tu-zi.com/api/log/get-request

Preview guide

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

# Retrieve request image or task results

Retrieve image results by request ID. The following is this gateway’s public contract.

## Endpoint and authentication

`GET https://api.tu-zi.com/api/log/get-request`

Transport: json

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

```http
Authorization: Bearer YOUR_API_KEY
```

## Query parameters

| Field | Type | Required | Description / constraints |
| --- | --- | --- | --- |
| request_id | string | Yes | Request ID of the original image call, not a task ID. Example: YOUR_REQUEST_ID |

## 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.

## Code examples

### curl

```bash
curl --request GET 'https://api.tu-zi.com/api/log/get-request?request_id=YOUR_REQUEST_ID' \
  --header 'Authorization: Bearer YOUR_API_KEY'
```

### python

```python
import json
import os
import requests

url = "https://api.tu-zi.com/api/log/get-request?request_id=YOUR_REQUEST_ID"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_API_KEY\"}")
headers["Authorization"] = "Bearer " + os.environ["API_KEY"]
response = requests.request("GET", url, headers=headers, timeout=120)
response.raise_for_status()
result = response.json()
if isinstance(result, dict) and (result.get("success") is False or result.get("error")):
    raise RuntimeError(json.dumps(result, ensure_ascii=False))
print(result)  # Also inspect protocol-specific status/code fields.
```

### javascript

```javascript
// Node.js 20+
const url = "https://api.tu-zi.com/api/log/get-request?request_id=YOUR_REQUEST_ID";
const headers = {
  "Authorization": "Bearer YOUR_API_KEY"
};
headers.Authorization = 'Bearer ' + process.env.API_KEY;
const response = await fetch(url, { method: "GET", headers });
if (!response.ok) throw new Error(await response.text());
const result = await response.json();
if (result?.success === false || result?.error) throw new Error(JSON.stringify(result));
console.log(result); // Also inspect protocol-specific status/code fields.
```

## Response fields

| Field | Type | Description / constraints |
| --- | --- | --- |
| status | string | succeeded, failed or processing_or_not_found. |
| request_id | string | Queried request ID. |
| data[].url | string | Recoverable image URL. |
| error.message | string | Failure information. |

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

```json
{
  "status": "processing_or_not_found",
  "request_id": "request_example",
  "data": []
}
```

## 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.

## Constraints

Accepts inference keys (current-key scope) or system tokens plus New-Api-User (current-account scope). Samples use an inference key. Includes async tasks and Midjourney; arbitrary text responses cannot be recovered. processing_or_not_found means either still processing or not found; use a polling deadline.

## Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-usage-request-result

This export contains documentation and examples only, without real credentials, account data or user requests.

Updated 2026-11-02 · Reviewed 2026-11-02

Endpoint and authentication

GET https://api.tu-zi.com/api/log/get-request

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

Accepts inference keys (current-key scope) or system tokens plus New-Api-User (current-account scope). Samples use an inference key. Includes async tasks and Midjourney; arbitrary text responses cannot be recovered. processing_or_not_found means either still processing or not found; use a polling deadline.

Query parameters

Field	Type	Required	Description / constraints
request_id	string	Yes	Request ID of the original image call, not a task ID. Example: YOUR_REQUEST_ID

Response fields

Field	Type	Description / constraints
status	string	succeeded, failed or processing_or_not_found.
request_id	string	Queried request ID.
data[].url	string	Recoverable image URL.
error.message	string	Failure information.

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

{
  "status": "processing_or_not_found",
  "request_id": "request_example",
  "data": []
}

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.

Document information and sources

Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-usage-request-result

This export contains documentation and examples only, without real credentials, account data or user requests.

Request examples

curl --request GET 'https://api.tu-zi.com/api/log/get-request?request_id=YOUR_REQUEST_ID' \
  --header 'Authorization: Bearer YOUR_API_KEY'

import json
import os
import requests

url = "https://api.tu-zi.com/api/log/get-request?request_id=YOUR_REQUEST_ID"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_API_KEY\"}")
headers["Authorization"] = "Bearer " + os.environ["API_KEY"]
response = requests.request("GET", url, headers=headers, timeout=120)
response.raise_for_status()
result = response.json()
if isinstance(result, dict) and (result.get("success") is False or result.get("error")):
    raise RuntimeError(json.dumps(result, ensure_ascii=False))
print(result)  # Also inspect protocol-specific status/code fields.

// Node.js 20+
const url = "https://api.tu-zi.com/api/log/get-request?request_id=YOUR_REQUEST_ID";
const headers = {
  "Authorization": "Bearer YOUR_API_KEY"
};
headers.Authorization = 'Bearer ' + process.env.API_KEY;
const response = await fetch(url, { method: "GET", headers });
if (!response.ok) throw new Error(await response.text());
const result = await response.json();
if (result?.success === false || result?.error) throw new Error(JSON.stringify(result));
console.log(result); // Also inspect protocol-specific status/code fields.