---
title: "Execute saved mapping with subroutes"
method: POST
path: "/Mapping/{mappingId}/{subroute}"
tags: ["Mapping"]
---

# Execute saved mapping with subroutes

`POST /Mapping/{mappingId}/{subroute}`

Same as `POST /Mapping/{mappingId}`, but path segments after the mapping ID are captured as routing metadata and exposed via `$fumeHttpInvocation`.
OpenAPI cannot model Express-style multi-segment wildcard routes. The actual server route supports an arbitrary number of path segments after `{mappingId}` (e.g. `POST /Mapping/{mappingId}/a/b/123`).
This path is documented with a single `{subroute}` segment for documentation purposes only. Swagger UI "Try it out" (and many generated clients) cannot reliably invoke the multi-segment form.

## Path parameters

- `mappingId` string, required
- `subroute` string, required

## Query parameters

- `verbose` string

## Request body

- object

## Response `200`

Mapping result (any JSON). When `?verbose` is enabled, returns a VerboseReport.

## Other responses

- `206` — Partial result
- `404` — Mapping not found
- `415` — Unsupported media type
- `422` — Compilation, transform, or evaluation failure

---

[API](https://skmtc.net/outburn-il/apis/fume-community-api.md) · [All operations](https://skmtc.net/outburn-il/apis/fume-community-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/outburn-il/fume-community-api/versions/38d0cabbc2ce/schema)