---
title: "Discussion on \"API-led design: RAML, API Designer, and mocking before you build\" | Hashnode"
description: "Discussion on \"API-led design: RAML, API Designer, and mocking before you build\". On a recent integration for a banking client, the team that designed the API contract before anyone wrote a line of Mule code shipped weeks ahead of the one that didn't. This is a practitioner's account of doing API-led design right: RAML i"
url: "https://hashnode.com/posts/api-led-design-raml-api-designer-and-mocking-before-you-build/6a5383000ab7994d80be50df"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [API-led design: RAML, API Designer, and mocking before you build](https://sapotacorpvn.hashnode.dev/api-led-design-raml-api-designer-and-mocking-before-you-build?utm_source=hashnode&utm_medium=feed)

On a recent integration for a banking client, the team that designed the API contract before anyone wrote a line of Mule code shipped weeks ahead of the one that didn't. This is a practitioner's account of doing API-led design right: RAML i

Jul 12 · 8 min read · sapotacorpvn.hashnode.dev  
Read the article

-   [#mulesoft](https://hashnode.com/tag/mulesoft)
-   [#salesforce](https://hashnode.com/tag/salesforce)
-   [#integration](https://hashnode.com/tag/integration)
-   [#api-led-connectivity](https://hashnode.com/tag/api-led-connectivity)
-   [#raml](https://hashnode.com/tag/raml)

## Written by

[SapotaCorp](https://hashnode.com/@sapotacorpvn)

@sapotacorpvn · Hanoi, Vietnam

  
[View profile](https://hashnode.com/@sapotacorpvn)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
