Skip to main content
POST
Query task status

Query task

Poll the Wizzx task_id returned by submit with the same API key. You can query via RESTful GET /api/v1/task/{task_id} (recommended), GET /api/v1/task/status?task_id={task_id}, or POST /api/v1/task/status. All three read stored task state without re-submitting work to the provider.
Or via POST:
Client-visible states are PENDING, QUEUED, PROCESSING, REVIEW_REQUIRED, SUCCEEDED, and FAILED. Internal DISPATCHING is returned as PROCESSING. Continue polling the same Task ID for non-terminal states. Do not automatically create a replacement task for an unknown state, REVIEW_REQUIRED, or an ambiguous submit response. If a task fails and its reserved credits are refunded (or was never charged), credits_deducted is 0.

Response

A successful task lists its media in result_urls. The field is unchanged for every model.

Music results

Finished music tasks also return a structured result object. Which fields are present depends on the action; fields without a value are omitted. Other models do not return result.
  • Tracks keep their order, even when a track has no audio_url (for example after upload).
  • For music tasks, result_urls lists every track audio_url, then the download files, then the music video. Text and analysis results such as lyrics, BPM, and MIDI have no URL; read them from result.
  • Media URLs are normally served from cdn.wizzx.ai. If copying a file to the CDN fails, the original URL is returned instead and may expire, so download results you want to keep.
  • Music tasks that finished before October 15, 2026 have no result.

Authorizations

Authorization
string
header
required

Wizzx API key. This is not a JWT.

Body

application/json
task_id
string<uuid>
required

Wizzx task ID returned by submit.

Response

Current task state

code
enum<integer>
required
Available options:
0
message
string
required
Example:

"success"

data
object
required
request_id
string<uuid>
required