> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acedata.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Suno Audio Availability Check API

> Suno Music Generation integration guide - Ace Data Cloud

`POST /suno/availability` searches for positive evidence that audio can continue to be processed on the current route based on `audio_id`. It can be called before operations such as continuation and cover; the result only reflects the status at the time of checking and does not guarantee that a specific operation will succeed. This API returns synchronously, requires an API Token, and currently does not deduct Credits.

`audio_id` is the song ID returned by a completed Suno task, not `task_id`.

```bash theme={null}
curl -X POST 'https://api.acedata.cloud/suno/availability' \
  -H 'Authorization: Bearer YOUR_API_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"audio_id":"33333333-3333-4333-8333-333333333333"}'
```

Successful response example:

```json theme={null}
{
  "success": true,
  "task_id": "11111111-1111-4111-8111-111111111111",
  "trace_id": "22222222-2222-4222-8222-222222222222",
  "data": {
    "id": "33333333-3333-4333-8333-333333333333",
    "available": true
  }
}
```

When the check succeeds, `data.available` can only be `true`. The “offline” status returned by some routes cannot prove that subsequent operations such as continuation cannot succeed, so this API returns `503 availability_unknown` when it cannot be confirmed and will not return `false`. An invalid `audio_id` format returns 400, and rate limiting or upstream failures also return error responses. The status may still change between completion of the check and the actual operation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.