• POST https://v2.api.audio/content/script
• PUT https://v2.api.audio/content/script
• GET https://v2.api.audio/content/scripts
• GET https://v2.api.audio/content/script/{scriptId}
• DELETE https://v2.api.audio/content/script/{scriptId}
• POST https://v2.api.audio/content/generate/advert
• POST https://v2.api.audio/speech/tts
• GET https://v2.api.audio/speech/tts
• DELETE https://v2.api.audio/speech/tts/{speechId}
• POST https://v2.api.audio/speech/tts/reduce
• POST https://v2.api.audio/speech/tts/remove_padding
• POST https://v2.api.audio/speech/tts/annotate
• GET https://v2.api.audio/speech/sts/voices
• POST https://v2.api.audio/speech/sts
• GET https://v2.api.audio/speech/sts/{pipelineId}
• POST https://v2.api.audio/production/mix
• POST https://v2.api.audio/production/validate
• POST https://v2.api.audio/production/mixes
• GET https://v2.api.audio/production/mix/{productionId}
• DELETE https://v2.api.audio/production/mix/{productionId}
• GET https://v2.api.audio/production/mix/presets
• POST https://v2.api.audio/delivery/encoder
• GET https://v2.api.audio/delivery/encoder/presets
• POST https://v2.api.audio/delivery/connectors/julep
• PUT https://v2.api.audio/delivery/connectors/authenticate-julep
• GET https://v2.api.audio/delivery/connectors/status
• GET https://v2.api.audio/delivery/connectors/status/{deliveryId}

Why is this change happening?

All functionality in these endpoints is available via AudioStack's 2.0 API - documented here - offering superior quality, performance, scalability and functionality. We are removing legacy endpoints to focus on delivering quality, scalable audio via the v2.0 API.

What should I do?

If you are using any of the endpoints listed for deprecation, contact your account manager (or [email protected]) for guidance on migrating your API integration.