AsyncAPI Best Practices

general > asyncapi-operation-operationId-uniqueness

Guidance / Message

operationId must be unique across all the operations (except these one defined in the components).

Examples

valid

/endpoint:
subscribe:
  operationId: subs-ops
  message:
    x-pageSize: 5

invalid

/endpoint:
subscribe:
  operationId: subs-ops
  message:
    x-pageSize: 5
/anotherendppoint:
  subscribe:
    operationId: subs-ops
    message:
      x-pageSize: 5

Applies to AsyncAPI

Constraint

Type: Rego Validation