Skip to content
HiAPI Docs
HiAPI
Playground Get API Key
English
English 中文

Mureka 9.5 Instrumental API

POST Base URL: https://api.hiapi.ai /v1/tasks

Image, video, and audio models are called through theUnified Async API POST /v1/tasks endpoint; only the input fields differ (see input parameters below).

Model summary

Model name mureka-9.5/instrumental
Type Audio generation (instrumental)
Endpoint POST /v1/tasks
Pricing See HiAPI Pricing

Mureka 9.5 instrumental turns a text description of genre, mood, instruments, and arrangement into an instrumental track without vocals, for scores, background music, and standalone instrumentals.

Production guidance

Production guidance
  • For production, pass callback.url at the top level of the request body so HiAPI can notify your service when the task reaches a terminal state.
  • GET /v1/tasks/:id is better for local debugging, low-volume jobs, or fallback reconciliation if a callback is missed.
  • Use callback.when=final. Both success and fail are terminal states, so your service should deduplicate by taskId.

Best suited for

Video and ad scoring

Describe the instrumental around an intro, transition, or product sequence and generate a bed that drops into the timeline.

prompt
Podcasts and spoken content

Generate vocal-free intros, beds, and section transitions that stay out of the narrator's way.

prompt
Games and ambient spaces

Build ambient music from mood and instrumentation descriptions for galleries, game scenes, or immersive experiences.

prompt

Request parameters

model string required

Fixed value mureka-9.5/instrumental.

example mureka-9.5/instrumental
input object required

Business parameters. Put instrumental inputs here.

prompt string required

Instrumental description, 1–1,024 characters: genre, mood, instruments, tempo, and arrangement. This route does not generate sung vocals.

callback object optional

Optional callback configuration. When set, HiAPI notifies your service when the task reaches a terminal state.

url string required

Required when callback is set; HTTPS URL that receives terminal task notifications.

example https://your-domain.com/hiapi/callback
when enum optional

Callback trigger timing. Use final.

default final enum: final

Example requests

Cinematic orchestral instrumental

A wide film-score cue described with a piano ostinato, swelling strings, low brass, and soft timpani.

Request body
{
  "model": "mureka-9.5/instrumental",
  "input": {
    "prompt": "Cinematic orchestral instrumental with a fragile piano ostinato, evolving string swells, low brass and soft timpani, hopeful then resolute, wide film-score reverb."
  }
}

Getting the result

  1. A successful submission returns a taskId immediately; it does not wait for generation.
  2. In production, prefer the callback.url terminal notification; poll GET /v1/tasks/:id for local debugging.
  3. When status=success, find the type=audio entry in output and download the audio from its url.
  4. If status=fail, correct the request using the returned error instead of retrying the same invalid input.

FAQ

What does the instrumental route require?

A prompt is required, 1–1,024 characters, describing genre, mood, instruments, tempo, and arrangement.

Does the instrumental route include vocals?

No. It generates instrumental music without sung vocals. Use the lyrics-to-song route when you need vocals.

Can I upload a reference track, clone a voice, or provide a melody?

The current route does not accept reference tracks, voice cloning, or melody uploads. It accepts a text description only.

How is it billed?

Billing is a fixed charge per successful generation, independent of description length and output duration. See the live pricing page for the current rate. View pricing

Next steps