API Reference

Retrieve a Suno v2 task

Retrieve a Suno v2 task. The following is this gateway’s public contract.

GET https://api.tu-zi.com/suno/v2/fetch/{task_id}
Preview guide

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

Preview guide

Retrieve a Suno v2 task

Updated · Reviewed

Endpoint and authentication

GET https://api.tu-zi.com/suno/v2/fetch/{task_id}

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

Only Suno v2 tasks in the current account and application scope are returned. Foreign, missing and non-v2 tasks return errors. Use returned public asset IDs for follow-up actions, not provider IDs.

Path parameters

FieldTypeRequiredDescription / constraints
task_idstringYesPublic task ID returned by this gateway. Example: YOUR_TASK_ID

Response fields

FieldTypeDescription / constraints
codestringsuccess for a successful query.
data.task_idstringPublic gateway task ID.
data.statusstringSUCCESS / FAILURE are terminal; other states are pending.
data.progressstringTask progress.
data.fail_reasonstringFailure reason when present.
data.dataobject | arrayAction result, including musics or other outputs; resource IDs are gateway public IDs.

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

{
  "code": "success",
  "message": "success",
  "data": {
    "task_id": "task_example",
    "status": "SUBMITTED",
    "progress": "0%"
  }
}

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.