DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Building Multi-Rail Payment Failover to Stop Latency Spikes and Double Debits
  • GET, POST, PUT, DELETE: Choosing HTTP Verbs in a Real .NET Core Web API, Not Just by the Textbook
  • Delegated Transport, Forked Authorization: Where Chat and AI-Agent Integrations Actually Break
  • A Non-Expiring AKS Deployment Token Could Read Secrets Across Three Namespaces

Trending

  • The "Just Read the Code" Myth Is Killing Your AI Workflow
  • Spring Security JWT Validation Best Practices
  • Idempotency Under Concurrency: Why Your Application Check Isn't the Last Line of Defense
  • How to Hide Sensitive Information Before You Share a File

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Data Engineering
  3. Databases
  4. RAML: Designing a Simple API

RAML: Designing a Simple API

In this tutorial, learn how to design a simple API by working with the RESTful API Modeling Language, complete with code and screenshots to illustrate the process.

By 
Tirapa Reddy Tondapu
·
Apr. 26, 17 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
22.4K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in
  • The following procedure covers how to design and implement an online REST service and consume that service. The procedure describes an example API that has only one resource; for simplicity, the user details were hard-coded you can also implement a corresponding backend connection to get the actual user data based on the inputs.

Creating the Sample Project Name User_Information

Once you have started your Anypoint studio, click on File, New, and Mule Project as shown in the below screenshot:

Create a mule project

Enter the Project Name as `User_Information` and then click on Finish tab.

Project Folder Structure

Generating a Sample RAML Definition API (Creating sample.raml)

Right click on project (User_Information), click on New, click on RAML API Definition, and then enter the file name as "sample." Click on finish.

Creating Sample.raml file

As you can see in the below screenshot, a sample.raml file as been created with title "Sample AP."

Sample API

Configure a Service endpoint and document section using baseUri and documentation properties at the root level of RAML file, as shown in this screenshot:

Service Endpoint and documentation

baseUri: https://www.tirapareddy.com:8081/api

documentation:
- title: Home Page for Sample API
content: |
This example documentation forms part of a tutorial for a 
[RAML Turorial](https://docs.mulesoft.com/api-manager/design-raml-api-task) article.

Create a sample user-example.json response JSON file.

 {
"name":"Tirapa Reddy Tondapu",
"company":"Eidiko Systems Integrators",
"location":"Hyderabad"
}

Create a sample resource to get user details as shown in the below code block.

/userInfo/{id}:
  get:
  description: Retrieves details of a particular users
  responses:
    200:
      body:
        application/json:
          example: !include user-example.json


Now we have created a resource named "userInfo" that can be used to retrieve particular user information.

Generate Corresponding Flows for This Resource (userInfo) From the RAML File

In order to generate corresponding flows for the above userInfo resource we need to right click on sample.raml==> click on Mule ==> click on Generate flows from RAML as shown in the attached screenshot:Generating Flows

As you can see in the above screenshot once you click on "generate flows from RAML", it will generate sample.xml mule cofiguration file containing below items along with the  below attached HTTP listener  congiguration(i.e the application is running at hot "localhost" and post:8081)

  1. APIKit Router.

  2. APIKit Console.

  3. userInfo resource flow.

  4. Global exception strategy.HTTP Listener Configurations

Running The User_information Project

Right click on the project "User_information" then click "Run as" and then click on " Mule Application."

Once you click on "Mule Application," the project will be deployed as shown in the attached screenshot.

Deployed

As the project has been deployed, now it is accessible from http://localhost:8081/console once you browse this URL you will be able to see the below API details:

Sample API Console

You can now access the API resource "userInfo" by clicking on GET and the providing any id value as shown in the attached screenshot:

Final Output page of Sample API

You can also see entire source code at https://github.com/tirapa-eidiko/RAML_User_Information.

Thanks & Regards,

Tirapa Reddy Tondapu

API

Opinions expressed by DZone contributors are their own.

Related

  • Building Multi-Rail Payment Failover to Stop Latency Spikes and Double Debits
  • GET, POST, PUT, DELETE: Choosing HTTP Verbs in a Real .NET Core Web API, Not Just by the Textbook
  • Delegated Transport, Forked Authorization: Where Chat and AI-Agent Integrations Actually Break
  • A Non-Expiring AKS Deployment Token Could Read Secrets Across Three Namespaces

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook