Open StephenHodgson opened 1 month ago
Hi Stephen, can you expand on what your use case is?
We aren't currently planning on supporting a sound generation history. Instead we'd recommend you follow this process for generation and then store it on your side: https://elevenlabs.io/docs/api-reference/how-to-use-text-to-sound-effects
Hi Stephen, can you expand on what your use case is?
We aren't currently planning on supporting a sound generation history. Instead we'd recommend you follow this process for generation and then store it on your side: https://elevenlabs.io/docs/api-reference/how-to-use-text-to-sound-effects
The use case is having a complete, functional and useful API surface.
Without history there is no point to offering API access to sound generation API.
Ideally the API surface should be similar to the existing history endpoints for speech to text.
These changes are necessary to fully support the API in my Unity Game Engine and DotNet foss API clients:
Path: /api-reference/sound-generation
Missing:
get:
/v1/sound-generation/history
get:/v1/sound-generation/history/{clip-id}
get/v1/sound-generation/history/{clip-id}/audio