March 2019 Summaries

OpenAPI Specification (OAS) 3 introduced the concept of Server Variables, allowing for configurable parts of an API's URL, and this feature is now supported in API Explorer for users utilizing JWT Login. Server Variables enable API consumers to change specific segments of a URL, such as {username}, {port}, and {basePath}, enhancing customization for different users. The recent update has added support for enums and manual entry of Server Variables, which facilitates the creation of unique URLs for customers while maintaining a default setup for those not logged in. Although there are some limitations, such as lack of support for manually defined APIs within ReadMe, the feature represents a significant step forward in API customization, with further improvements being open for discussion with ReadMe's support team.

Ryan, originally from Sandy, UT, is relishing a break from the snowy Utah mountains and is eager to deliver an exceptional Customer Success experience for ReadMe clients. He is an active individual who enjoys a variety of sports, hiking, camping, and walking his dog, Walter. Recently, Ryan taught himself to juggle, so he might be seen practicing his new skill by tossing and catching objects.

ReadMe has introduced a new feature in its enterprise suite that allows the creation of read-only members within child projects, enhancing the ability to control API visibility among different user groups while supporting authentication protocols like SAML and OAuth. This feature enables read-only users to access projects without any administrative privileges and allows them to request access to specific projects, which triggers email notifications to project owners. Users requesting access are displayed in the enterprise project members section, and projects utilizing SAML need to be configured to "Project Members Only" to facilitate these changes. This update aims to simplify the provisioning of private APIs and improve user management within organizations.