---
title: "Discussion on \"APIKit: turning a RAML spec into a routed implementation\" | Hashnode"
description: "Discussion on \"APIKit: turning a RAML spec into a routed implementation\". When a design team hands you a finished RAML spec, the worst thing you can do is hand-roll a Choice router that compares URIs for every endpoint. APIkit reads the contract and routes requests to flows for you. Here's how scaffolding, implem"
url: "https://hashnode.com/posts/apikit-turning-a-raml-spec-into-a-routed-implementation/6a53826bfb8200cfb0715f09"
---

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

Discussion

# [APIKit: turning a RAML spec into a routed implementation](https://sapotacorpvn.hashnode.dev/apikit-turning-a-raml-spec-into-a-routed-implementation?utm_source=hashnode&utm_medium=feed)

When a design team hands you a finished RAML spec, the worst thing you can do is hand-roll a Choice router that compares URIs for every endpoint. APIkit reads the contract and routes requests to flows for you. Here's how scaffolding, implem

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

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

## Written by

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

@sapotacorpvn · Hanoi, Vietnam

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

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
