June 13, 2022 (12 months ago)
We have some good news! Mux users can now easily interact with our API via our officially supported Postman collection. By forking our collection via the “Run in Postman” button in docs and adding the forked collection to your Postman workspace, you get the following benefits:
First, you need to briefly navigate away to click an orange button in our docs that says “Run in Postman.” Clicking this button will trigger the user flow to fork a Postman collection.
Once you click the button, a new tab will open up, prompting you to click another orange button that says “Fork collection.” Click that button.
Next, Postman will prompt you to create a name for your forked collection — just something to let it know that you’re a clone and not the original. You’ll also have to select which of your existing Postman workspaces you want to copy or fork this collection into. Keep in mind that if you fork this collection into a public collection, it will technically be viewable by other people.
Voila! You can now easily make API requests for Mux Video or Mux Data in Postman with minimal setup. Note: You will still need to set up your personal authentication details.
We made it possible for you to fork our Postman collection and stay up to date with our API because we believe it will help you get familiar faster and interact more seamlessly with our product. We’d love to know whether this works out for you. You can let us know by leaving a comment at the bottom of the respective docs page for the Postman collection.
If you have any questions or want to chat, I’m all ears @clearlythuydoan on Twitter 💃🏻
No credit card to start. $20 in free credits when you're ready.
Vercel's Edge Config can come in handy in many different ways. See how we used it to cut down on the amount of spam we were dealing with from our forms.
By Justin Sanford
With lazy-loading and a blurhash placeholder, we make the loading experience of Mux Player feel great in our Next.js app
By Darius Cepulis
While hunting for a pesky live streaming bug, we discovered that virtual load balancers don’t always simulate their physical counterparts the way you might expect.
By Dmitry Ilyevsky