---
title: "Tutorial for creating interactive consoles with RAML"
date: 2015-10-03
description: "Following on the Swagger tutorial I posted about the other week, this week I’d like to point you to my RAML tutorial. This is part of my larger..."
canonical_url: https://idratherbewriting.com/2015/10/03/RAML-tutorial-notes/index.html
---

> For AI agents: a documentation index is available at https://idratherbewriting.com/llms.txt. Markdown versions of all pages are available by appending .md to any page URL.

# Tutorial for creating interactive consoles with RAML

> This is a tutorial for creating interactive consoles with the RAML spec. The interactive console allows users to try out your API directly in the documentation.

Following on the [Swagger tutorial](https://idratherbewriting.com/2015/09/14/swagger-tutorial/) I posted about the other week, this week I’d like to point you to my [RAML tutorial](https://idratherbewriting.com/learnapidoc/pubapis_raml/).

This is part of my larger API doc course, so in this tutorial I’m taking a simple Weather API from Mashape and putting the API’s endpoints, parameters, and sample responses into the RAML spec. Then I publish that API into several different RAML outputs using API Console, Mulesoft’s Anypoint Platform, and RAML2HTML.

In comparing RAML with Swagger, I think both are strong specifications for APIs. They’re definitely the top two. I like RAML’s tooling and design philosophy a lot, but Swagger probably has a more robust community. Both have a lot of momentum going on.