Suno Voice Get Verification Phrase API

Short version: this one is a stub. It's meant to fetch the verification phrase and its details for a voice task - the read-back companion to the node that generates the phrase - but in the shipped pack it can't send a request, so it fails with "This KIE API page has not been resolved yet."

That's not a broken install, a missing key, or a typo in your graph. It's how the pack is built.

Why it happens

The pack's whole design is that it doesn't hardcode KIE's model list. On first launch it reads KIE's official API documentation index and generates a node per callable page, enriching each from the endpoint's own docs. New models become nodes without waiting for a plugin release, which is genuinely the right call for a provider that ships as fast as KIE does.

The cost is that a page which doesn't parse - say the docs render client-side and the fetch returns the page shell rather than a request schema - produces a node with a name and nothing behind it. KIE's page for this endpoint (docs.kie.ai/suno-api/suno-voice-validate-info) is one of those. The pack registers it, and the node's summary in the catalog is literally JavaScript scraped from the docs site, which tells you everything about why the parser gave up.

So method, endpoint and the parameter list are all empty, and executing the node raises the "not been resolved yet" error before any network call happens. Nothing is charged.

Reading the widgets honestly

Because there's no schema, the input list fell back to the pack's generic skeleton: a required multiline prompt. Treat it as a label, not an input - there's no documented field for it to populate here.

timeout_seconds (30–7200, default 1200) is the standard completion wait, and expert_override_json ({} by default) is the escape hatch for request-body fields on thinly documented endpoints. Know its limit: it overrides payload keys. It cannot invent an endpoint. With no URL resolved, there is nothing for that JSON to ride on.

The declared outputs - audio, url, all_urls_json, task_id, raw_json, credits_consumed, credits_left - are the audio-family default signature, not evidence that a phrase lookup returns media. If you ever do get this node talking, raw_json is where the answer will be.

What actually works today

First, try to let the pack fix itself. Run the catalog sync node, restart ComfyUI, and check again - the pack re-reads KIE's docs at most once a day, and unparsed pages do get picked up on later passes. KIE • Inspect API Definition (Advanced) tells you what the catalog knows right now, which distinguishes "unparsed" from "you're looking at the wrong node".

If it's still a stub, the working routes around it are KIE • Universal Market Task (Advanced) for anything that goes through KIE's Market task endpoint, and the pack's advanced raw-request node when you know the documented path and want to call it directly with a custom_endpoint. Neither is as pleasant as a purpose-built node. Both return real data.

And if all you need is "did my voice task finish", don't wait on this node at all - Suno Voice Check Availability already does that job for the voice-creation flow, and KIE • Task Status does a single non-blocking poll of any task ID.

Install and key

cd ComfyUI/custom_nodes
git clone https://github.com/felipederosilva/ComfyUI-KIE-Nodes-Next
pip install -r requirements.txt

Restart ComfyUI, then set the key once under Settings → KIE.ai Nodes Next → Connection - the pack validates it against KIE before saving and shows a masked fingerprint plus a CONNECTED status and your balance. ComfyUI Manager installs the pack too; search "KIE.ai Nodes Next". Nothing downloads locally, because all of this runs on KIE's machines and bills per call.

Last thing, and it applies to every node in this family: because a wrapper node carries your API key and talks to the internet by design, it's the one kind of custom node worth a look before you run it. This pack keeps the full key backend-only and out of workflow JSON, which is the right behaviour - verify that for any KIE pack you try, including the more widely used ComfyUI-Kie-API.