API Reference
Batch retrieve legacy Suno tasks
Batch retrieve legacy Suno tasks; requires a configured legacy Suno channel.
Preview guide
Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.
Updated · Reviewed
Endpoint and authentication
POST https://api.tu-zi.com/suno/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
Before calling
- Examples use this site's address. For another gateway, replace only the site address and keep the full endpoint path.
- Replace resource placeholders
YOUR_TASK_ID: obtain task/request IDs from the same account's real responses and use provider versions/buttons documented by the linked protocol. Do not send placeholders. - Resource IDs such as 123 are examples. Read real IDs from your own list endpoint before retrieving or modifying them; batch operations also require owned IDs.
- 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
- Empty ids returns an empty array.
- Only matching accessible tasks are returned; ordering is not guaranteed.
- GET also accepts id, ids[] and repeated parameters.
- This feed is a gateway task query, not a raw provider song list.
Minimal request example
{
"ids": [
"YOUR_TASK_ID"
]
}
Confirming success
Check HTTP status, the business status in the body and the required result fields. Do not rely only on HTTP 200 or the script exit code.
- Legacy Suno first requires code=success.
- Submission data is a task ID string; after retrieval reaches data.status=SUCCESS inspect media in data.data. Stop on FAILURE.
Body parameters
| Field | Type | Required | Description / constraints |
|---|---|---|---|
| ids | array | No | Gateway task IDs; comma-separated for GET, array for POST. Example: ["YOUR_TASK_ID"] |
Response fields
| Field | Type | Description / constraints |
|---|---|---|
| code | string | success for a successful query. |
| data[] | object | Accessible task, same shape as legacy single-task retrieval. |
Illustrative response; some endpoints show essential fields only. Optional fields may be absent.
{
"code": "success",
"data": []
}
Errors and retries
Check HTTP status and protocol-specific errors; do not mix error formats across protocols.
- 401/403: check credentials and permissions.
- 429: classify temporary throttling, exhausted quota, or service capacity failure; only transient failures merit bounded backoff.
- 5xx: inspect the gateway, upstream, and model/channel configuration.
Error bodies may contain error/message/code depending on the protocol.
- Use bounded exponential backoff for reads encountering transient errors; fix parameter, authentication, quota, or configuration failures first.
- Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.
兔子API