API Reference

Suno feed lookup

Suno feed lookup; requires a configured legacy Suno channel.

GET https://api.tu-zi.com/v1/suno/feed
Preview guide

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

Preview guide

Suno feed lookup

Updated · Reviewed

Endpoint and authentication

GET https://api.tu-zi.com/v1/suno/feed

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.
  • 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_KEY environment variable or replace YOUR_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.

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.

Query parameters

FieldTypeRequiredDescription / constraints
idsstringNoGateway task IDs; comma-separated for GET, array for POST. Example: YOUR_TASK_ID

Response fields

FieldTypeDescription / constraints
codestringsuccess for a successful query.
data[]objectAccessible 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.