Restlet Studio Supports RAML 1.0 API Specification

Restlet today announced the release of a new version of Restlet Studio with support for the latest RAML 1.0 specification, in addition to full support for OAS 2.0. Restlet Studio is used by businesses of any size to visually and collaboratively design and document REST APIs that are at the core of their digital projects.  

DevOps teams use Restlet Studio to develop microservices and backends in addition to design public APIs. By committing to the RAML and OAS standards, including the import, export and translation between those specifications, Restlet helps companies design APIs that can be used in tools from any vendor, including Restlet’s own Platform.

Restlet is a founding member of the Open API Initiative (OAI), the organization behind OAS. As part of today’s Restlet Studio product announcement, Restlet’s CTO is joining the RAML Workgroup to help steer the RAML specification.

“We’re excited that Restlet’s CTO is joining the RAML Workgroup and that Restlet is supporting RAML 1.0 in Restlet Studio,” said Uri Sarid, CTO of MuleSoft and primary author of the RAML specification. “With RAML support, Restlet Studio can help a broader range of companies unlock the potential of the API economy and join an ecosystem that makes API-first design simple.” 

“Our new version of Restlet Studio with RAML support will help companies move to API-first software design,” said Jerome Louvel, Founder and CTO of Restlet. “I am proud to be a member of the RAML Workgroup. Restlet Studio customers can take advantage of the new RAML 1.0 specification today. In the future, we are committed to supporting RAML’s advanced API design capabilities such as elements reusability within an API and across several APIs. Restlet supports RAML alongside OAS across our REST platform and I look forward to closer collaboration between RAML and OAS communities.” 

Restlet Studio now supports both RAML 0.8 and 1.0 specifications with translation between the versions as well as OAS versions 1.2 and 2.0. This is important for businesses that want to either 1) migrate from RAML 0.8 to RAML 1.0 or 2) combine RAML and OAS in the same project to use RAML’s design strengths and OAS for their production API gateway.

Disclosure: Mulesoft is the parent company of ProgrammableWeb

Be sure to read the next API Design article: Twilio's Top 3 Tips For Building APIs So Developers Actually Use Them