A summary of the changes that we are making to our Media API endpoints and the effects on you.
We are continuing our evolution of MK.IO from our roots as a replacement for Azure Media Services into our own thing — and the next step is to give our media API paths a bit of a revamp.
What does this mean to you? Well, our documentation will stop referring to /api/ams/<project>/<resourceType> and will instead refer to /api/v1/projects/<project>/media/<resourceType> . That's it.
What do you need to do? Nothing. We're committed to backwards compatibility, so while we are using new paths for these endpoints, and while the docs will guide users to those new paths, we will still support the old paths for the foreseeable future. We promise.
After all, we still support the legacy /subscriptions/<subscription>/resourceGroups/<resource_group>/providers/Microsoft.Media/mediaservices/<project_name>/<resourceType> paths!