Skip to main content
POST
Submit Music Cover Generation Task
  1. After submission, a task_id will be returned. If you provided a callback_url, when the task status becomes finished or failed, a POST request will be sent to the callback_url.
  2. Regardless of whether callback_url is provided, you can retrieve the response result through the unified Query Music Detail endpoint.

Usage Guide

  • This endpoint creates a cover version of an existing music track
  • Requires a valid task_id from a previously generated music task
  • The cover will be a new interpretation of the original track

Parameter Details

  • task_id (required): The task ID from a completed music generation task
    • Must be a valid task_id returned from the Generate Music or Extend Music endpoints
    • The original task must have completed successfully

Developer Notes

  • A cover can only be generated once per original task
  • Results are delivered via the callback URL when processing is complete

Authorizations

Authorization
string
header
required

All API endpoints require Bearer Token authentication.

Create an API key: sign in to PoYo, open Dashboard → API Key at poyo.ai/dashboard/api-key, and click to create a key.

Add it to the request header:

Body

application/json
model
enum<string>
required

API model identifier.

Must be generate-music-cover for this endpoint.

Available options:
generate-music-cover
Example:

"generate-music-cover"

callback_url
string<uri>
required

Webhook callback URL for result notifications.

The system will send POST requests to this URL when cover generation is complete, including task status and results.

Example:

"https://your-domain.com/callback"

input
object
required

Input parameters for cover generation

Response

200 - application/json

Task submitted successfully

code
enum<integer>
required

Business status code. 200 means success; any other value means the request failed. Always check this field: some validation errors return HTTP 200 with code: 400 in the body.

  • 200: Success
  • 400: Invalid request parameters
  • 401: Missing or invalid API key
  • 402: Insufficient credits
  • 403: Permission denied
  • 404: Resource not found
  • 408: Request timeout
  • 429: Rate limit exceeded
  • 500: Internal server error
  • 502: Upstream service error
  • 503: Service unavailable

See Error Codes for details.

Available options:
200,
400,
401,
402,
403,
404,
408,
429,
500,
502,
503
Example:

200

data
object
required