Sign in
Mapping

Execute 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.

post/Mapping/{mappingId}/{subroute}

Path parameters

mappingIdstring required

The ID of the saved mapping

subroutestring required

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

verbosestring

When set to true (case-insensitive) or 1, returns the full evaluation report instead of the raw result.

Request body

object required

Response

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

Changes

Changed in 2 of the 8 revisions of this API.35

  • be37a3a526362See the full diff
    • ▲

      removed the enum value 1 from the query request parameter verbose

      request-parameter-enum-value-removed

    • ▲

      removed the enum value true from the query request parameter verbose

      request-parameter-enum-value-removed

  • 811964783e7e15See the full diff
    • ▲

      the query request parameter verbose was restricted to a list of enum values

      request-parameter-became-enum

    • ○

      added the new enum value 1 to the query request parameter verbose

      request-parameter-enum-value-added

    • ○

      added the new enum value true to the query request parameter verbose

      request-parameter-enum-value-added

    • ○

      response property line list-of-types was narrowed by removing types string from media type application/json of response 422

      response-property-list-of-types-narrowed

    • ○

      response property position list-of-types was narrowed by removing types string from media type application/json of response 422

      response-property-list-of-types-narrowed

    • ○

      response property start list-of-types was narrowed by removing types string from media type application/json of response 422

      response-property-list-of-types-narrowed

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog