The current version of the RAML specification is 1.0 - and you can find it here.

RAML is a language for the definition of HTTP-based APIs that embody most or all of the principles of Representational State Transfer (REST). The RAML specification (this document) defines an application of the YAML 1.2 specification that provides mechanisms for the definition of practically-RESTful APIs, while providing provisions with which source code generators for client and server source code and comprehensive user documentation can be created.

Why not pay us a visit on raml.org? You will find tons of information around RAML such as a tutorial, what the RAML Workgroup is, RAML projects, a forum, and a lot more.

All you need is an editor of your choice - we recommend either MuleSoft's API Designer or API Workbench; but any text editor will do just fine.

Now you only need to do is to write the design for your first endpoint

#%RAML 1.0
title: Hello world # required title

/greeting: # optional resource
  get: # HTTP method declaration
    responses: # declare a response
      200: # HTTP status code
        body: # declare content of response
          application/json: # media type
            # structural definition of a response (schema or type)
            type: object
            properties:
              message: string
            example: # example how a response looks like
              message: "Hello world"

Interested? Learn more about the syntax in the RAML 1.0 specification or take a look at some examples.

• Tutorial - In progress to be updated to 1.0
• Advanced Tutorial - In progress to be updated to 1.0
• Community Sneak Peaks
• RAML MVP Program - Currently in beta
• Examples
• Wiki
• Projects

We welcome any contributions from the community! You can contribute or provide feedback for the RAML Specification in different ways depending on your intentions. The following table illustrates the different ways to help us not only to improve the documentation of the specification, but also RAML itself.

• @ramlapi
• [email protected]
• forum
• chat
• Stack Overflow
• Github Issues

Branding Guidelines