Anypoint Best Practices

(6 reviews)

path-params

general > path-params


Guidance

Path parameters are correct and valid if the following requirements are met:
- For every parameter referenced in the path string, for instance: `/users/{userId}`, the parameter must be defined in
either the `path.parameters` or `operation.parameters` objects. Nonstandard HTTP operations will be silently
ignored.
- Every `path.parameters` and `operation.parameters` parameter must be used in the path string.

Applies to EndPoint

Constraint

Type: Rego Validation

Reviews

TypeRuleset
OrganizationMuleSoft
Published by
MuleSoft Organization
Published onOct 11, 2022
Asset overview

Asset versions for 1.0.x

Asset versions
VersionActions
1.0.3
1.0.2
1.0.1
1.0.0