· reAPI Team
Mureka api tutorial
Mureka API on reAPI takes lyrics and an optional style prompt, returns a task ID, then song URLs after completion. Follow the documented request and polling flow.
A Mureka API request on reAPI needs the model ID mureka-v9-song and written lyrics. The documented workflow returns a task ID first, then song URLs after completion. It accepts up to 3 songs per request and supports mp3, wav, and flac output.[1]
This tutorial covers that specific reAPI interface, checked against its public documentation and implementation on October 22, 2026. The examples have not been submitted to generate audio. They demonstrate request construction and result handling; they do not establish generation speed, musical quality, reference fidelity, or the latest Mureka model. The cover is a conceptual illustration, not an audio-generation result.
At a glance
- Put the words to sing in
lyrics; put musical direction in the optionalprompt.[1] - Start with
number_of_songs: 1; the documented range is 1–3 and quantity affects the charge.[1] - Submit once, retain the returned
id, and poll that task until it finishes.[2] - Read
output.audio_urlsaftercompletedand copy files to your own storage if you need lasting access.[2]
mureka api key
The requests below go to reapi.ai and require a reAPI API key. In the reAPI dashboard, open API Keys, create a key, and store the value when it is shown. Send it as Authorization: Bearer .... The authentication guide describes key creation and authentication errors.[3]
Keep the key on your server or in a secret manager. The shell variable REAPI_API_KEY below stands for that secret; it is not a value supplied by this tutorial. Never include a live key in client-side JavaScript, screenshots, or a public repository. An account or key for a different service is not a substitute for a credential issued by reAPI.
mureka api docs
The Mureka V9 Song reference separates the text to sing from instructions about the music. lyrics is required and accepts up to 3000 characters. The optional prompt accepts up to 1024 characters and can describe genre, mood, instruments, vocal tone, or tempo.[1]
For example, put your verse and chorus text in lyrics, and a direction such as “soft piano pop with restrained percussion” in prompt. These are illustrative inputs, not a tested recipe. If the words belong in the vocal performance, putting them only in the style prompt does not satisfy the required lyrics field.
| Field | Documented input | First-request choice |
|---|---|---|
model | mureka-v9-song | Use the exact identifier. |
lyrics | Required; up to 3000 characters | Provide your own written lyrics. |
prompt | Optional; up to 1024 characters | Describe the desired musical style. |
number_of_songs | Integer 1–3; default 1 | Use 1 to request one song. |
output_format | mp3, wav, flac; default mp3 | Choose the format your application needs. |
reference_id, vocal_id, melody_id | Optional existing reference IDs | Omit unless you already have valid IDs. |
The reference fields accept IDs, not local filenames, audio URLs, or free-form descriptions. This tutorial does not provide an upload endpoint or a way to mint those IDs. Leave the fields out for the basic lyrics-and-style workflow; add one only when you have a valid existing reference for the intended field. The presence of a reference control does not prove how closely a generated song will follow it.[1]
Mureka api tutorial
This is a documentation-based request example. The short lyrics are illustrative text. Replace them with your own material and set the key in your server environment before choosing to run it. Submitting a generation request can incur charges.
curl https://reapi.ai/api/v1/audio/generations \
-H "Authorization: Bearer $REAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "mureka-v9-song",
"lyrics": "Morning light across the floor\nI leave a note beside the door",
"prompt": "Soft piano pop with restrained percussion",
"number_of_songs": 1,
"output_format": "mp3"
}'Save the id returned by that POST with the submitted settings. Assign it to TASK_ID and request its status with the same authentication method:
curl "https://reapi.ai/api/v1/tasks/$TASK_ID" \
-H "Authorization: Bearer $REAPI_API_KEY"The polling response determines what your application should do next.[2]
status | Application behavior |
|---|---|
processing | Keep the task pending. Do not treat a task ID as a finished audio file. |
completed | Read output.audio_urls and offer the returned files to the user. |
failed | Read error and usage.credits; stop waiting for a success result. |
A polling timeout in your application does not establish that generation failed. Keep the task ID so you can check it again, rather than automatically creating another generation request. The task reference documents polling and errors. For HTTP 429, respect Retry-After; do not immediately repeat the same request in a tight loop.
mureka api pricing
The documented billing unit is a generated song. number_of_songs is the quantity control; prompt, output format, and the optional reference fields are not separate price dimensions in this model's documented contract.[1] Check the current estimate on the Mureka V9 Song model page with the quantity you intend to request.
Polling itself does not consume credits. usage.credits is the task's settled whole-credit summary, so read it together with status: a zero while processing is not a free-generation offer. A failed task can report zero or a retained charge; do not assume every failure means a full refund.[2] A fresh POST for another variation is a new generation request, not a status check.
Mureka api download
After completed, handle output.audio_urls as an array, even when you requested one song. The documented output has one URL per generated song, using the selected format. Avoid silently retaining only the first result if your application lets users request more than one.[1]
Download the returned files and store them under your own retention policy when you need an archive. The task contract does not guarantee permanent storage of result URLs.[2] Keep the task ID, request settings, status, and saved file locations together so an operator can distinguish a pending job from a completed song that has not yet been copied.
For a first Mureka API integration, use the smallest request above, implement all three task states, and inspect the resulting audio before relying on it in a production workflow. The model page provides the current estimate, and the API reference supplies the full field contract.
Related API queries
mureka v9 api
This guide covers mureka-v9-song on reAPI. The identifier fixes the scope of the example; it is not a claim that V9 is the latest Mureka release.
mureka api documentation
The linked reAPI model reference documents this endpoint and these fields. Documentation for another interface may use different authentication, paths, or parameters.
mureka api cost
Check the model page with your chosen song quantity. Use the task settlement to inspect the eventual charge.
mureka api platform
The platform used by the examples is reAPI. Keep the base URL, credential issuer, and request schema together when configuring a client.
References
[1] Mureka V9 Song API. Reviewed October 22, 2026.
[2] Tasks. Reviewed October 22, 2026.
[3] Authentication. Reviewed October 22, 2026.