Owlet Weekly Update (Week of March 29)

Hello and welcome to another weekly update! If you're dialed into all things ReadMe, you'll know that we officially launched ReadMe Recipes last week 🎊 we've been subtly teasing it for months here in the Owlet Weekly Update and we couldn't be more excited that it's finally out in the wild! Be sure to check out our latest blog post to see the incredible stuff that our customers are already whipping up with ReadMe Recipes. 🧑‍🍳

As an avid reader of the ReadMe Changelog, you'll also know that we've been cooking up some big redesigns for the API Reference. Happy to report that we've been making great progress and that we've been hosting sneak peek events with some of the masterminds behind this initiative! You can sign up for one of the upcoming sessions here 👀

As for this release, we're still continuing to keep things on the lighter (but nevertheless substantial) side as we continue to work on these bigger initiatives behind the scenes. This week, we're shipping improvements to api and a few tiny fixes in the Enterprise dashboard. More below! 🥗

• Remember api? The Node.js SDK that's custom-tailored to your API? Well we just shipped v3.0, making it easier than ever to peel back the layers and access the sweet fruits of your API response. In other words, API responses are automatically parsed based on content type! For an example of this, check out the Node (simple) code samples in our API reference docs. 🍌
• This release addresses an issue where users were having trouble accessing certain sections of the Enterprise dashboard related to custom login and user management. 🔐

Thanks for reading and for being a part of the ReadMe community, folks!

—Kanad and the ReadMe Team

📘

What is the Owlet Weekly Update?

Thanks for tuning in to another edition of our _Owlet Weekly Update**—an _owlet-sized update (posted every week to the ReadMe Changelog) on the product updates we're shipping here at ReadMe. We'd love to hear what you think of these updates at [email protected]!