ElevenLabs music compose schemas are missing #86
Send to my agentProblem#
GET /v1/schemas/elevenlabs and GET /v1/openapi/elevenlabs publish one music path: v1/music/video-to-music.
The upstream spec at https://api.elevenlabs.io/openapi.json also has these JSON routes:
| Path | operationId | Request | Response |
|---|---|---|---|
POST /v1/music | generate | application/json | audio/* |
POST /v1/music/detailed | compose_detailed | application/json | multipart/mixed |
POST /v1/music/stream | stream_compose | application/json | audio/* |
POST /v1/music/plan | compose_plan | application/json | application/json |
Each request model_id enum is music_v1, music_v2, music_v2_5.
A read of those endpoint ids returns 404 unknown_schema. Example: GET /v1/schemas/elevenlabs/audio/v1/music?kind=input.
POST /v1/music/video-to-music is a different operation. Its body is multipart/form-data and it takes video files. It reuses the same MusicModelID enum, and that is the only music schema published today.
GET /v1/models?provider=elevenlabs returns 11 rows. Every row has schemaEndpointId: v1/text-to-speech/{voice_id}. No music_v* id is in that list.
Impact#
A client that composes music calls POST /v1/music, not video-to-music. The only published model_id enum is on the video route, so a schema sync has to read the wrong endpoint. TanStack AI's ElevenLabs adapter calls music.compose (POST /v1/music) and hit this while syncing model ids.
Ask#
Publish input schemas for v1/music, v1/music/detailed, v1/music/stream, and v1/music/plan from the upstream OpenAPI. Include those paths in GET /v1/openapi/elevenlabs.
Acceptance#
GET /v1/schemas/elevenlabs/audio/v1/music?kind=inputreturns 200.- Its
model_idenum lists the current music ids (music_v1,music_v2,music_v2_5today). GET /v1/openapi/elevenlabsincludes/v1/music.
tombeckenham added labelsbug
tombeckenham closed this
Sign in to join this conversation.