When working with asynchronous processes like music generation, voice cloning, or instrumental extraction, waiting for a task to complete can slow down your workflow. That’s where webhooks come in handy. Webhooks allow Musicgpt to notify your application the moment a task is completed. You’ll get all the necessary data — including the audio URL — without needing to constantly poll our API.Documentation Index
Fetch the complete documentation index at: https://docs.musicgpt.com/llms.txt
Use this file to discover all available pages before exploring further.
How It Works
- Set the
webhook_urlwhen submitting your conversion request. - Musicgpt will send a POST request to that URL when the task is completed.
- Your server can then parse the response and proceed with post-processing or user notifications.
Sample Payload
Here’s what a typical webhook payload looks like:
🔗 Set the webhook_url to an endpoint on your server — this is where Musicgpt will notify you once the generation is done.
Preliminary Response
When you initiate a conversion request, Musicgpt will immediately respond with a preliminary response that includes:success: whether the task was successfully initiatedtask_id: a unique ID you can use to track the conversion
💡 Can’t Use a Webhook?
No problem — if you’re running code on a client device or you don’t have a public server, you can always check the conversion status manually using our helper endpoint: 👉 Get Conversion by ID✅ Why Use Webhooks?
- No need for polling or delays
- Works in the background
- Instantly delivers results
- Ideal for automations and server workflows