Anypoint Best Practices

operations-must-have-descriptions

general > operations-must-have-descriptions


Guidance / Message

Provide descriptions for the operations.

Examples

valid

/events:
  get:
    displayName: get
    description: Gets a stream of results
    responses:
      200:
        description: Ok!
        body:
          application/json:
            type: string

invalid

/events:
  get:
    displayName: get # missing description
    responses:
      200:
        body:
          application/json:
            type: string

Applies to Operation

Constraint

Type: Declarative Validation
TypeRuleset
OrganizationMuleSoft
Published by
Mulesoft Organization
Published onOct 26, 2026
Asset overview

Asset versions for 1.7.x

Asset versions
VersionActions
1.7.0

Tags