Cookie Preferences
We use cookies to personalize content and analyze traffic. See our Cookie Policy.
No output yet. Submit the form to generate content.
Transparent pricing with no hidden fees. Pay as you go.
| Rule & Modality | Channel | Credits | Price (USD) | Official / Reference Price | Daily Savings |
|---|---|---|---|---|---|
Suno voice-check musicSuno | Starter | 1per run | $0.005 | - | - |
Complete guide to using Suno
Use the suno/voice-check API on ApiPass to verify whether an already generated Suno custom voice is ready for music generation workflows. Submit the Generate Voice task ID, receive a unified ApiPass task ID, and read the final availability state through the standard task record endpoint.
Suno Voice Check is a lightweight availability check for custom voices created through the Suno voice workflow. It should be used after suno/voice-generate succeeds and you have the Generate Voice task ID. The API checks availability only; it does not create a new voice and does not replace the voice validation or voice generation steps. Because the upstream operation is synchronous, ApiPass tasks usually move directly to success or fail, while still using the unified /api/v1/jobs/createTask and /api/v1/jobs/recordInfo task record flow for compatibility, tracking, and refund handling.
Verify whether a previously created Suno custom voice can be used with supported Suno music generation APIs. The result is returned as data.isAvailable inside the parsed resultJson value.
Even though the check is synchronous, ApiPass returns a standard taskId from /api/v1/jobs/createTask. Query /api/v1/jobs/recordInfo with that ApiPass task ID to retrieve success, fail, resultJson, failCode, and failMsg fields.
Use this API after suno/voice-generate completes successfully. The task_id value must be the Generate Voice provider task ID, not the ApiPass task ID returned by the voice-check request and not the suno/voice-validate task ID.
The create request requires only input.task_id, a non-empty string containing the successfully created custom voice Generate Voice task ID. ApiPass also accepts input.taskId and input.task as aliases at the input layer.
Parse data.resultJson from the task record to read data.isAvailable. A true value means the custom voice can be used by supported Suno interfaces; false means the request succeeded but the voice is not currently available.
Voice checks usually complete quickly and move directly to success or fail. Clients should still use the ApiPass recordInfo endpoint to read the final result and keep behavior consistent with other ApiPass task APIs.
Add an availability gate before launching music generation with a custom voice. Your application can check data.isAvailable and enable the next step only when the voice is ready.
Build dashboards that show validation, generation, and availability states for custom voices. Use the ApiPass task record to display success, fail, failCode, failMsg, and the parsed availability result.
Create backend workflows that wait for suno/voice-generate to succeed, extract the correct provider task ID, run suno/voice-check, and continue only when the voice is available.
Use each voice endpoint for the correct part of the custom voice workflow.
suno/voice-validate is used earlier in the workflow to generate a validation phrase from the source human voice. Its task ID is not the correct task_id for suno/voice-check.
suno/voice-generate creates the custom voice from the validation recording. After it succeeds, use its Generate Voice provider task ID as input.task_id for suno/voice-check.
suno/voice-check only verifies whether the generated custom voice is available for use. It returns availability through resultJson.data.isAvailable and does not create or modify the voice.
input.task_id must be the Generate Voice provider task ID from a successful suno/voice-generate task. If the Generate Voice task was created through ApiPass, first query that ApiPass task record and use the upstream provider task ID from that record.
task_id must be a non-empty string. Arrays, numbers, booleans, and empty strings are not supported. ApiPass accepts task_id, taskId, and task aliases in input, then forwards the normalized task_id field.
When data.isAvailable is false, the request itself may still be successful. Treat false as an unavailable voice state, and check failCode or failMsg only when the task state is fail.
Run the required voice validation and voice generation flow first. Wait until suno/voice-generate succeeds before calling suno/voice-check.
Send a POST request to /api/v1/jobs/createTask with model set to suno/voice-check and input.task_id set to the Generate Voice provider task ID. ApiPass returns a unified taskId for the check record.
Call /api/v1/jobs/recordInfo with the ApiPass taskId returned by the create request. Parse data.resultJson and read data.isAvailable to decide whether the custom voice can be used.
The API page shows the parameter schema, but Suno also has several business-specific mode combinations and callback rules that are easy to miss.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Submit a Suno voice availability check for a previously generated custom voice.
The API accepts a JSON payload with the following structure:
1{
2 "model": "suno/voice-check",
3 "channel": "auto",
4 "input": {
5 "task_id": "voice-generate-task-id"
6 }
7}modelRequiredstringThe public model name. This value must be fixed as suno/voice-check.
"suno/voice-check"
channelOptionalstringOptional APIPASS provider routing mode. The default channel is auto; APIPASS automatically allocates tasks across available providers based on real-time pricing and stability metrics. starter is ultra-low-cost with limited quotas and weaker stability; regular is standard and much cheaper than official APIs with moderate stability; official uses the model native API with high stability, fast task execution, and official pricing.
The default value for the channel parameter is auto. APIPASS automatically allocates tasks across available providers based on real-time pricing and stability metrics. starter is ultra-low-cost with limited quotas and weaker stability; regular is standard and much cheaper than official APIs with moderate stability; official uses the model native API with high stability, fast task execution, and official pricing.
Available options:
auto
The input object contains the voice check parameters.
input.task_idRequiredstringThe successfully created Suno custom voice task ID to check for availability.
Use the ApiPass Generate Voice task ID from a successful suno/voice-generate task. ApiPass also accepts input.taskId and input.task as aliases, but sends the field to ApiPass as task_id.
"voice-generate-task-id"
1curl --request POST \
2 --url https://api.apipass.dev/api/v1/jobs/createTask \
3 --header 'Authorization: Bearer <APIPASS_API_KEY>' \
4 --header 'Content-Type: application/json' \
5 --data '{
6 "model": "suno/voice-check",
7 "channel": "auto",
8 "input": {
9 "task_id": "voice-generate-task-id"
10 }
11 }'1{
2 "code": 200,
3 "message": "success",
4 "data": {
5 "taskId": "task_xxxxxxxxxxxxxxxx"
6 }
7}codeStatus code, 200 for success, others for failure.
messageResponse message. When the request fails, this contains the error description.
data.taskIdApiPass task ID used to query the voice check result through the Query Task API.
MiniMax
MiniMax
MiniMax Music 1.5 AI music generation model, supports lyrics and style prompt to generate music
Starting from
0 credits
Starting from
0 credits