# Hand-built listener flows and APIkit scaffolding

*MuleSoft Developer Study Guide · Building API Implementation Interfaces · Last updated October 28, 2026 · https://www.certifyforce.com/study-guide/mulesoft-developer/building-api-implementation-interfaces/hand-built-listener-flows-and-apikit-scaffolding*

How to implement an API specification by hand with HTTP Listener paths, URI parameter placeholders and Allowed methods, what you lose without APIkit, and how Anypoint Studio scaffolds a RAML or OAS specification into a main flow, a console flow and one flow per resource and method.

- Certification: Salesforce MuleSoft Developer
- Exam section: Building API Implementation Interfaces
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-developer

**Official exam objective:**

> Manually build API implementations from an API specification, RAML or not.

## What the exam expects

- Configure an HTTP Listener by hand so one flow implements one resource and method of a specification: Path with `{param}` placeholders, Allowed methods, and the Base path on the listener configuration.
- Predict which listener receives a request when paths overlap, and what a listener does with undeclared methods.
- Name what a hand-built implementation must do itself because no APIkit Router validates requests against the RAML.
- Scaffold flows in Anypoint Studio from a local RAML file, an Exchange asset or Design Center, and know that OAS scaffolds only from Exchange.
- Recognise the scaffolded project: main flow, console flow, per-method flows, `apikit:config` and the `src/main/resources/api` folder.
- Key terms: **resource-action pairing** (a resource plus the method on it, the unit APIkit generates a flow for); **URI parameter placeholder** (`{param}` in a listener path that captures a segment); **Allowed methods** (listener setting that restricts HTTP methods); **scaffolding** (Studio generating flows from a specification); **APIkit Router** (processor that validates requests against the specification and routes them to flows).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Path placeholders | `*` matches anything; `{param}` matches and captures to the URI parameters map | [Configure HTTP Listener Source](https://docs.mulesoft.com/http-connector/latest/http-listener-ref) |
| Allowed methods default | All methods; restrict on the Advanced tab | [Configure HTTP Listener Source](https://docs.mulesoft.com/http-connector/latest/http-listener-ref) |
| Overlapping paths | Request goes to the most specific source | [Configure HTTP Listener Source](https://docs.mulesoft.com/http-connector/latest/http-listener-ref) |
| Base path | Set on the listener configuration; applies to all its listeners | [Configure HTTP Listener Source](https://docs.mulesoft.com/http-connector/latest/http-listener-ref) |
| Request validation | Done by APIkit Router, not by a plain listener | [Build an Application from an API Specification](https://docs.mulesoft.com/mule-runtime/latest/build-application-from-api) |
| OAS scaffolding | Only from published Exchange assets; Studio has no OAS 3.1 | [APIkit for REST Scaffolding Reference](https://docs.mulesoft.com/apikit/latest/apikit-4-scaffolding-reference) |
| Scaffolded flows | Main flow, console flow, one flow per action-resource-content-type | [APIkit for REST Scaffolding Reference](https://docs.mulesoft.com/apikit/latest/apikit-4-scaffolding-reference) |
| RAML location | `src/main/resources/api` | [Build an Application from an API Specification](https://docs.mulesoft.com/mule-runtime/latest/build-application-from-api) |
| `api` attribute | URL, relative path under `src/main/resources/api`, or API Sync resource path | [APIkit for REST Module Reference](https://docs.mulesoft.com/apikit/latest/apikit-4-xml-reference) |

## Check yourself

- Why does a scaffolded implementation flow have no event source?
- When does a wildcard at the end of a listener path help?
- How many implementation flows does scaffolding generate?
- What does a listener path of `account/{accountId}/*` match?

## Sources

- [Configure HTTP Listener Source](https://docs.mulesoft.com/http-connector/latest/http-listener-ref)
- [Build an Application from an API Specification](https://docs.mulesoft.com/mule-runtime/latest/build-application-from-api)
- [APIkit for REST Scaffolding Reference](https://docs.mulesoft.com/apikit/latest/apikit-4-scaffolding-reference)
- [Building, Implementing, and Testing a REST API](https://docs.mulesoft.com/apikit/latest/apikit-4-implement-rest-api)
- [APIkit for REST Module Reference](https://docs.mulesoft.com/apikit/latest/apikit-4-xml-reference)
- [APIkit for REST](https://docs.mulesoft.com/apikit/latest/apikit-4-for-rest)
- [Step 3. Develop the API](https://docs.mulesoft.com/general/api-led-develop)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 7 linked practice questions, and unlimited timed mock exams are included with the MuleSoft Developer pack (USD $19): https://www.certifyforce.com/practice-exams