Changes to Retrieve registered Flows

Changed in 2 of the 5 revisions of this API.●2○9

1. Aug 8, 2025696ee83009f6○1
2. Aug 6, 202582f6f0eba091●2○8

What changed

• Aug 8, 2025696ee83009f6○1See the full diff
  • ○

    api operation id FlowListFlows removed and replaced with 11_list_flows

    api-operation-id-removed

• Aug 6, 202582f6f0eba091●2○8See the full diff
  • ●

    removed the optional property items from the response with the 200 status

    response-optional-property-removed

  • ●

    removed the optional property offset from the response with the 200 status

    response-optional-property-removed

  • ○

    api operation id FlowListFlows was added

    api-operation-id-added

  • ○

    api tag Flow Control added

    api-tag-added

  • ○

    api tag Flow Management removed

    api-tag-removed

  • ○

    query request parameter offset list-of-types was widened by adding types null

    request-parameter-list-of-types-widened

  • ○

    query request parameter q list-of-types was widened by adding types null

    request-parameter-list-of-types-widened

  • ○

    for the query request parameter offset, the type was generalized from string to no type

    request-parameter-type-generalized

  • ○

    for the query request parameter q, the type was generalized from string to no type

    request-parameter-type-generalized

  • ○

    added the non-success response with the status 400

    response-non-success-status-added

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