v1
latestOpenAPI 3.0.32026-07-1710820.0 KBExecute saved mapping with subroutes
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
The ID of the saved mapping
Documentation-only placeholder for the wildcard route remainder. For real multi-segment usage, call the endpoint as /Mapping/{mappingId}/... with one or more additional path segments (e.g. /Mapping/{mappingId}/a/b/123).
Query parameters
When set to true (case-insensitive) or 1, returns the full evaluation report instead of the raw result.
Request body
Response
Mapping result (any JSON). When ?verbose is enabled, returns a VerboseReport.