API Reference

Retrieve Suno v2 tasks in a batch

Retrieve Suno v2 tasks in a batch. The following is this gateway’s public contract.

POST https://api.tu-zi.com/suno/v2/fetch
Preview guide

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

Preview guide

Retrieve Suno v2 tasks in a batch

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/suno/v2/fetch

Transport: json

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

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Minimal request example

{
  "ids": [
    "YOUR_TASK_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.

Constraints

Returns only matching accessible v2 tasks in the current account/application scope. Missing, foreign and non-v2 IDs are omitted. Empty ids returns an empty array; this is not proof of task completion.

Body parameters

FieldTypeRequiredDescription / constraints
idsstring[]YesPublic gateway task IDs. Example: ["YOUR_TASK_ID"]

Response fields

FieldTypeDescription / constraints
codestringsuccess for a successful query.
data[]objectAccessible v2 tasks; item fields follow the single-task query.

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

{
  "code": "success",
  "message": "success",
  "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.